-
Notifications
You must be signed in to change notification settings - Fork 42
Settle in Parallel #695
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
Merged
Merged
Settle in Parallel #695
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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.
Case 2 (settle failed but model succeeded) calls
handleResolveResponseafter settle has already sent a 402 response, which will cause an Express error when trying to send a second response to the same request.View Details
📝 Patch Details
Analysis
Double response error in handleX402Request Case 2
What fails: In
handleX402Request()(packages/app/server/src/handlers.ts, lines 46-62), when settle fails but the model request succeeds (Case 2), the code callsmodelRequestService.handleResolveResponse()after settle has already sent a 402 response viabuildX402Response(), causing Express to throw "Error: Can't set headers after they are sent to the client".How to reproduce:
buildX402Response(req, res, maxCost)which sendsres.status(402).json(resBody)modelRequestService.handleResolveResponse(res, isStream, data)which calls eitherres.json(data)(non-streaming) orres.end()(streaming)Result: Error thrown and logged by error handler: "Error: Can't set headers after they are sent to the client". While the 402 response reaches the client (and the error handler checks
res.headersSentbefore attempting another response), this is incorrect behavior - no error should be thrown since the 402 response is the correct outcome.Expected: When settle fails and sends a 402 response indicating payment is required, no subsequent response should be attempted. The 402 response should be the final response to the client.
Root cause: Express.js specification requires exactly one response per HTTP request. Once response headers are sent, attempting to set additional headers or send another response violates this protocol and throws an error.