Did you read the technical details? This was a bug in the way Redis-py handled requests that were cancelled before a response was returned to the user.
So? You own the stack. All that had to be said was there was a bug in the way requests were handled in a library. The open source part is not even needed.
I think the mention of exactly where is useful to this audience. Other people using the same open-source library might realize --- oh, we've run into that bug but never realized it. Low probability, sure, but nonetheless.
OpenAI could have simply named the library up front instead of stressing that it is open source. This would have alerted people who use the library while at the same time avoiding the suggestion that it being open source was part of the problem.
They tweeted few days back there was a bug in an open source library. That's the main issue.
Yes, and this is still the sole responsibility of OpenAI. They chose to include redis-py without warranties and are responsible for their own QA on any product built on it.
I reject the premise this is a bug. The author picked this implementation with whatever side effects. The author might want some requests to cancel in some situations. It's upto OpenAI to decide if the implementation works for their setup.