Live data from Hacker News

OpenAI: Increased errors across API and ChatGPT

status.openai.com

61–67 of 67 posts

Re: OpenAI: Increased errors across API and ChatGPT

#61

Does anyone know if Azure's OpenAI Studio is down as well? For everyone using ChatGPT APIs in production, this needs to be the most straightforward failover mechanism. Using this to plug our open-source tool https://github.com/Marvin-Labs/lbgpt which allows ChatGPT consumers to quickly load balance and failover between OpenAi and Azure models.

Azure OpenAI is running normally https://azure.status.microsoft/en-us/status

Re: OpenAI: Increased errors across API and ChatGPT

#62
post #33

Earlier quoted context omitted.

The question at hand is pretty easy to test manually and the information you get is much more useful. You will get to see the exact behavior for yourself, can easily build on the test case as related questions come up, and you know the information you are getting is correct rather than a hallucination. Copying information from ChatGPT is the newer version of blindly copying answers from StackOverflow. It often works…

> The question at hand is pretty easy to test manually and the information you get is much more useful. This approach can be hazardous to the health of the product you're building. For example, if you take this approach to answer the question of "what happens if I have two connections to a MySQL database, start a transaction in one of them and insert a row (but don't commit) and then issue a SELECT which would show t…

> you could easily end up with bugs that only show up when the transaction isolation level changes from how you tested it.

In fact it's very likely you would. You have to understand the transaction semantics and test with all the isolation levels and database platforms you intend to support. If you don't know this, you need to learn more about relational databases before building a product on top of them.

Re: OpenAI: Increased errors across API and ChatGPT

#63

Earlier quoted context omitted.

> The question at hand is pretty easy to test manually and the information you get is much more useful. This approach can be hazardous to the health of the product you're building. For example, if you take this approach to answer the question of "what happens if I have two connections to a MySQL database, start a transaction in one of them and insert a row (but don't commit) and then issue a SELECT which would show t…

> you could easily end up with bugs that only show up when the transaction isolation level changes from how you tested it. In fact it's very likely you would. You have to understand the transaction semantics and test with all the isolation levels and database platforms you intend to support. If you don't know this, you need to learn more about relational databases before building a product on top of them.

> If you don't know this, you need to learn more about relational databases before building a product on top of them.

And now extend this principle to everything in the stack.

Re: OpenAI: Increased errors across API and ChatGPT

#64

Earlier quoted context omitted.

> you could easily end up with bugs that only show up when the transaction isolation level changes from how you tested it. In fact it's very likely you would. You have to understand the transaction semantics and test with all the isolation levels and database platforms you intend to support. If you don't know this, you need to learn more about relational databases before building a product on top of them.

> If you don't know this, you need to learn more about relational databases before building a product on top of them. And now extend this principle to everything in the stack.

You should at least have some basic ideas about your stack.

Re: OpenAI: Increased errors across API and ChatGPT

#65

Earlier quoted context omitted.

> If you don't know this, you need to learn more about relational databases before building a product on top of them. And now extend this principle to everything in the stack.

You should at least have some basic ideas about your stack.

Agreed. But also if you suddenly find that the precise behavior of one of the parts of your stack matters, you would be well advised to search the internet about how exactly that bit works in practice and whether there are any nonobvious footguns in addition to your empirical testing and the stuff that the manual claims is true.

Re: OpenAI: Increased errors across API and ChatGPT

#66
post #56

Earlier quoted context omitted.

On a recent interview of Sam Altman (Hard Fork podcast) he mentioned that due to the load they have been trying to make optimizations, disable certain features, etc. so it’s not outside the realm of possibility that some tweak caused this.

I think one of the harder things about developing these models is that regressions are hard to figure out or even detect.

That’s a good point, would be curious to understand more what the testing setup is like for these kinds of systems.

Re: OpenAI: Increased errors across API and ChatGPT

#67

I think we need a new type of status page or at least a public version number on llms, yesterday for me GPT4 started giving nonsense super generic answers, like it was hardly reading what I wrote, and today it is back to top notch performance. I think they were trying to make the model more efficient or something but I just saw a massive decrease in the quality of output. From my side though, there is no version numb…

I experience the same with the API, it simply ignored all system message. This things should be told beforehand clearly
Post reply on HN