-
Notifications
You must be signed in to change notification settings - Fork 9.5k
feat[Go]: implement chat write and session-create APIs #15667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
hunnyboy1217
wants to merge
1
commit into
infiniflow:main
Choose a base branch
from
hunnyboy1217:feat/go-chat-write-apis
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
For github.com/gin-gonic/gin v1.9.1, what error does Context.ShouldBindJSON return for (1) an empty request body and (2) malformed JSON?💡 Result:
In gin-gonic/gin v1.9.1, the
Context.ShouldBindJSONmethod utilizes the standard library'sencoding/jsonpackage to decode the request body [1][2]. Consequently, it returns the following errors for the specified scenarios: (1) Empty Request Body: When the request body is empty,ShouldBindJSONreturns anio.EOFerror [3][4]. This occurs because the underlyingjson.Unmarshalprocess attempts to read from the request body stream, which is empty [4]. (2) Malformed JSON: When the JSON is malformed (e.g., missing brackets, trailing commas, or invalid syntax),ShouldBindJSONreturns a*json.SyntaxError[1][2]. In some cases involving incomplete or unparseable payloads, it may also return anio.EOFor an "unexpected EOF" error [5]. It is important to note that becauseShouldBindJSONreads the request body stream, subsequent attempts to read or bind the body will result in anio.EOFerror [4][1][6]. If you need to bind the body multiple times, you should useContext.ShouldBindBodyWithJSONinstead, which caches the body in the context [3][6].Citations:
Reject malformed JSON payloads instead of silently defaulting the session name.
ShouldBindJSONin gin v1.9.1 returnsio.EOFfor an empty body, but malformed JSON returns*json.SyntaxError(and in some cases an unexpected-EOF-style error). Since the code currently discards the bind error, malformed payloads also fall through and create a session with the default"New session".💡 Suggested change
📝 Committable suggestion
🤖 Prompt for AI Agents