anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

SDK throws 'Unexpected end of JSON input' on empty response bodies #4790

New Issue
Closed
opened 2026-02-16 17:45:26 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:45:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @coleleavitt on GitHub (Jan 11, 2026).

Originally assigned to: @thdxr on GitHub.

Bug Description

The SDK crashes with SyntaxError: Unexpected end of JSON input when the server returns an empty response body without proper Content-Length: 0 header or 204 status code.

Steps to Reproduce

  1. Make an API call that returns an empty body with status 200
  2. SDK attempts to parse the empty body as JSON
  3. Crashes at client.gen.ts:167

Error Message

SyntaxError: Unexpected end of JSON input
    at json (unknown)
    at <anonymous> (../sdk/js/src/v2/gen/client/client.gen.ts:167:33)

Expected Behavior

  • Empty responses should be handled gracefully (return {})
  • Malformed JSON should provide actionable error messages with status code and URL

Root Cause

  1. Client-side: SDK only checks for status === 204 or Content-Length === "0" before attempting JSON parse. Empty body with 200 status and no Content-Length header falls through to response.json() which throws.

  2. Server-side: OPTIONS handler in /packages/console/app/src/routes/zen/v1/models.ts returns status: 200 with null body instead of status: 204.

Proposed Fix

  • Read response as text first, only parse if non-empty
  • Add try-catch with contextual error messages for malformed JSON
  • Fix server to return proper 204 status for empty responses

Related Issues

  • #7715 - Same bug report (duplicate)
  • #7618 - Similar fix attempt (error messages only, doesn't prevent the crash)

Not Related (different root causes)

  • #2188, #3034, #5890, #7692 - These are about model-generated malformed JSON, not SDK response parsing
Originally created by @coleleavitt on GitHub (Jan 11, 2026). Originally assigned to: @thdxr on GitHub. ## Bug Description The SDK crashes with `SyntaxError: Unexpected end of JSON input` when the server returns an empty response body without proper `Content-Length: 0` header or `204` status code. ## Steps to Reproduce 1. Make an API call that returns an empty body with status 200 2. SDK attempts to parse the empty body as JSON 3. Crashes at `client.gen.ts:167` ## Error Message ``` SyntaxError: Unexpected end of JSON input at json (unknown) at <anonymous> (../sdk/js/src/v2/gen/client/client.gen.ts:167:33) ``` ## Expected Behavior - Empty responses should be handled gracefully (return `{}`) - Malformed JSON should provide actionable error messages with status code and URL ## Root Cause 1. **Client-side**: SDK only checks for `status === 204` or `Content-Length === "0"` before attempting JSON parse. Empty body with `200` status and no Content-Length header falls through to `response.json()` which throws. 2. **Server-side**: OPTIONS handler in `/packages/console/app/src/routes/zen/v1/models.ts` returns `status: 200` with null body instead of `status: 204`. ## Proposed Fix - Read response as text first, only parse if non-empty - Add try-catch with contextual error messages for malformed JSON - Fix server to return proper 204 status for empty responses ## Related Issues - #7715 - Same bug report (duplicate) - #7618 - Similar fix attempt (error messages only, doesn't prevent the crash) ## Not Related (different root causes) - #2188, #3034, #5890, #7692 - These are about model-generated malformed JSON, not SDK response parsing
yindo closed this issue 2026-02-16 17:45:26 -05:00
yindo commented 2026-02-16 17:45:26 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 11, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #7715: Unexpected end of json

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 11, 2026): This issue might be a duplicate of existing issues. Please check: - #7715: Unexpected end of json Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:45:26 -05:00
Author
Owner
Copy Link
Copy Source

@jimgrubb commented on GitHub (Jan 11, 2026):

Affected Model: Zen GLM-4.7
Reproduced: 2 times
Rate limit error before crash:
High concurrency usage of this API, please reduce concurrency or contact customer... retrying in 17s attempt #5
Additional context: The JSON parsing error occurred after seeing rate limiting messages. May be related to truncated/retry responses under load.

@jimgrubb commented on GitHub (Jan 11, 2026): **Affected Model:** Zen GLM-4.7 **Reproduced:** 2 times **Rate limit error before crash:** High concurrency usage of this API, please reduce concurrency or contact customer... retrying in 17s attempt #5 **Additional context:** The JSON parsing error occurred after seeing rate limiting messages. May be related to truncated/retry responses under load.
yindo commented 2026-02-16 17:45:27 -05:00
Author
Owner
Copy Link
Copy Source

@dhruvkej9 commented on GitHub (Jan 12, 2026):

@thdxr any easy temp. way to fix it ??

Have to restart opencode mid-session due to this.

@dhruvkej9 commented on GitHub (Jan 12, 2026): @thdxr any easy temp. way to fix it ?? Have to restart opencode mid-session due to this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4790
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?