3 ms·
Didn't find this in the README: does it handle network/OpenAI errors via retries? In particular the very common "model is overloaded at the moment". It's fine
by H8crilA 3y ago
Didn't find this in the README: does it handle network/OpenAI errors via retries? In particular the very common "model is overloaded at the moment".
It's fine if not, I can imagine you want to keep it as simple as possible and outsource it to the library user.
- minimaxir 3y agoI was mixed about putting it in the base package but you can get the same behavior with the tenacity package.
- H8crilA 3y agoYeah, I understand. Maybe it would be good to add a comment on it in the README, since most people will hit this problem.
- mikeravkine 3y agoErrors are so common with these endpoints, not having retry out of the box just makes it harder to hack on which I think is against the spirit?
- Klathmon 3y agoOn the other hand, automatic retires can be suprising, especially when they don't completely understand the returned error and retry on errors they shouldn't. I just wasted a couple hours the other week due to langchainjs defaulting to retrying errors which were ultimately caused by timeouts and would never complete.