3 ms·
While there's not much for GitHub to gain from disclosing the faulty code, I still would've liked to see the actual (pseudo)code that caused the race condition
by trinovantes 6y ago
While there's not much for GitHub to gain from disclosing the faulty code, I still would've liked to see the actual (pseudo)code that caused the race condition
- sudhirj 6y agoYeah, for a code hosting site I’d expect some code examples of what happened so we can all check our code for the same mistakes.
- KronisLV 6y agoWhile GitHub's codebase may be a bit more complex than most of the other projects out there, i agree that a writeup of the bug would definitely be useful!
- denysvitali 6y agoYou probably can get the GitHub Enterprise version, "decompile" it and diff the sources
- TheDong 6y agoUnlikely. > The underlying bug existed on GitHub.com for a cumulative period of less than two weeks at various times between February 8, 2021 and March 5, 2021. > There is no indication that other GitHub.com properties or products were affected by this issue, including GitHub Enterprise Server Github enterprise does not include commit history, and the above two things together make it sound like this bug was in a change that was being slowly rolled out or a/b tested, and that never made it into a github enterprise release. It's unlikely anyone outside of github can shed light on this one.