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 you have an API route that is taking very long to respond, then call reload, the first request is not cancelled. This leads to a situation where the first response will start streaming, then when the second one (from the reload call) comes in, it will overwrite the first response, leading to confusing behavior and UI.
IMO the first request should be cancelled in this situation.
Code example
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
If you have an API route that is taking very long to respond, then call
reload
, the first request is not cancelled. This leads to a situation where the first response will start streaming, then when the second one (from thereload
call) comes in, it will overwrite the first response, leading to confusing behavior and UI.IMO the first request should be cancelled in this situation.
Code example
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: