[kungfooguru]

> But while it took some time for us to diagnose, as soon as we did, we merged and pushed a fix within a few hours.

The comment in the thread says on May 1, "We have a fix for this issue and it will be pushed on or before our next weekly push next Tuesday"

But it didn't go out until May 5.

[sicross]

We initially thought we had a fix, but upon further investigation, we discovered a deeper issue. I agree, we could have been better at updating the bug with this information.

In the meantime, the severity of the issue became more obvious, which is why we accelerated the fix and deployed it today (May 5th) ahead of the regular weekly push scheduled for tomorrow (May 6th).