Re:We found and fixed a rare race condition in our session h...
by petters on Thursday March 18, 2021 @06:23PM
(#26508157)
I agree with you in general, but in this particular case they knowingly deployed thread-unsafe code in production while increasing the threaded concurrency. That should have broken internal development rules.
[ Parent
| on HN ]
Re:We found and fixed a rare race condition in our session h...
by eli on Thursday March 18, 2021 @06:47PM
(#26508348)
Now imagine what happens behind the scenes at other service providers. Iād bet the ones that have policies that bury the details of incidents, on average, have worse problems.
Re:We found and fixed a rare race condition in our session h...
by yuliyp on Thursday March 18, 2021 @07:22PM
(#26508628)
Yes. Writing code with bugs breaks internal development rules. The issue wasn't thread-unsafe code. It was confusion about object lifecycle. An env object was assumed to no longer be used by the web framework after a request terminated, while in reality it was recycled for future requests as a performance optimization.