Closed krrishdholakia closed 9 months ago
Investigating this further. This is caused by our current implementation of streaming which try-excepts, and if it's an exception assumes the stream is exhausted and returned an empty response object.
However, this means that errors silently fail across all providers. Will need to actually find the finish reason raised and stop when that occurs.
If it's an exception have it enter our exception mapping logic.
Impacted providers:
Pushed in - 889679a0dd072760f80db043503d45b484062050
What happened?
Relevant log output
No response
Twitter / LinkedIn details
No response