> Instead, they frantically went through their git log to see what in the code base might have triggered this bug. This seems like you're embellishing this par

> Instead, they frantically went through their git log to see what in the code base might have triggered this bug. This seems like you're embellishing this part to tell a story? It's not supported by the linked post, and from the bugzilla bugs it seems like it was known almost immediately that the ESR builds were affected as well and so it almost had to be an external service, they just weren't sure which one at first.