Improve SSE error handling#1
Open
HeadBro1 wants to merge 1 commit into
Open
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.
Summary
usernamebefore using it as an AgentScope session id.API_KEYconfiguration to the frontend instead of leaving the chat response blank./healthendpoint for service checks.Why
The current
/streamhandler only prints agent exceptions on the server and then closes the stream. In the browser this shows up as a generic EventSource error or blank assistant response, which makes common setup/runtime problems difficult to diagnose. The handler also accepts arbitraryusernamevalues and passes them directly toJSONSession, so session ids are not constrained before being used for persistence.Validation
python3 -m py_compile chatbot.py