fix: Error handling for chats that are slow to respond#435
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds user feedback and robust error handling for slow or unresponsive chat requests in the chat UI. It introduces a "waiting too long" indicator if the server takes more than 20 seconds to respond, and implements a 60-second timeout for chat requests. Additionally, error messages are now more descriptive and user-friendly, helping users understand the nature of any issues encountered.
User feedback and UI improvements:
waitingTooLongstate and a corresponding UI indicator inChatPageto inform users when the server is taking longer than expected (after 20 seconds). This indicator provides feedback about possible server load and impending timeout. [1] [2] [3]Timeouts and error handling:
useChatStreaming, aborting the request and providing a clear error if no response is received in time. The timeout resets with each data chunk received. [1] [2] [3] [4]useChatStreamingto distinguish between different failure scenarios (timeout, no response, network error, server error) and show user-friendly error messages. [1] [2]