You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the ctx used by StreamPrediction is canceled, StreamPrediction will throw an error.
The expectation is that StreamPrediction stops processing without throwing an error.
The text was updated successfully, but these errors were encountered:
Hi @yan5xu. Thanks for reporting this. It was our intention for context cancellation to return without an error. Can you share what error is being produced?
Hi @yan5xu. Thanks for reporting this. It was our intention for context cancellation to return without an error. Can you share what error is being produced?
lol, below is the error msg I collected in the log
@yan5xu Thank you for clarifying. If the error happens because the context is canceled for the original HTTP request for the stream, I think it's reasonable to bubble that up. And on reflection, I think it's less confusing if context errors are always returned, even when used to cancel a stream. Would you agree with that?
In the meantime, my recommendation would be to check for context cancellation errors and handle those differently:
If the ctx used by StreamPrediction is canceled, StreamPrediction will throw an error.
The expectation is that StreamPrediction stops processing without throwing an error.
The text was updated successfully, but these errors were encountered: