mirror of
https://github.com/NikkeTryHard/zerogravity.git
synced 2026-04-25 07:05:58 +03:00
[GH-ISSUE #29] Upstream 400 Bad Request (Schema.ref 'QuestionOption') dropped with "no channel to forward it" #26
Labels
No labels
bug
enhancement
enhancement
notice
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zerogravity#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hwang-pixel on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/NikkeTryHard/zerogravity/issues/29
What happened?
When sending a request through the zerogravity MITM proxy, the upstream API (daily-cloudcode-pa.googleapis.com) returns a 400 Bad Request due to a schema validation error. Specifically, the upstream API complains that Schema.ref 'QuestionOption' was set alongside unsupported fields.
Instead of propagating this 400 error back to the client gracefully, the proxy logs a warning stating upstream error but no channel to forward it. This indicates a failure in error handling/forwarding, likely leaving the client hanging or experiencing an abrupt connection closure without knowing the actual API error.
How to reproduce
Just basic prompting, i dont know how but this is my prompt.
Diagnostic Report
Additional Context
My opencode.json
@NikkeTryHard commented on GitHub (Feb 20, 2026):
give me ur
zg report@hwang-pixel commented on GitHub (Feb 20, 2026):
@hwang-pixel commented on GitHub (Feb 20, 2026):
Here you go sir ^
@NikkeTryHard commented on GitHub (Feb 20, 2026):
see if fixed with v1.1.9
@NikkeTryHard commented on GitHub (Feb 20, 2026):
assume its fixed lol