AI API receipt · sgl-project/sglang

glm47 streaming parser emits tool-call arguments that are not valid JSON

sgl-project/sglang#43273 · upstream bug reproduced by running the issue's own reproduction

✓ Badgr rejects this response

Streamed arguments came out as '{"a": 1, 2}' (and '{"b": True}'), which no JSON parser accepts.

Outcome contract verdict: tool call arguments are not complete JSON. The attempt is recorded as failed (invalid_outcome) instead of a verified success, so it is not billed as a good answer and can fall back to another route.

What the upstream returned (replayed)

The output the bug produces, taken from the issue’s reproduction and fed to Badgr’s validators. Not a live provider call.

data: {"choices": [{"index": 0, "delta": {"tool_calls": [{"index": 0, "function": {"arguments": "{\"a\": 1, 2}", "name": "a"}}]}, "finish_reason": null}]}
data: {"choices": [{"index": 0, "delta": {}, "finish_reason": "tool_calls"}]}
data: [DONE]

Badgr receipt

Written by Badgr’s receipt ledger and read back from GET /v1/receipts/replay-sglang-43273-glm47-invalid-stream-json.

{
  "request_id": "replay-sglang-43273-glm47-invalid-stream-json",
  "status": "failed",
  "endpoint": "/v1/chat/completions",
  "stream": true,
  "failure_stage": "outcome_contract",
  "error_code": "invalid_outcome",
  "error_message": "Response did not satisfy the outcome contract: tool call arguments are not complete JSON",
  "retryable": true,
  "provider_mode": "replay",
  "routing_decision": "replayed_upstream_output",
  "created_at": "1791524108.887393"
}

Recorded 2026-10-09 in Badgr’s local development environment. Replay cases and verdicts are pinned by backend/test_ai_api_replay_cases.py.

← All AI API receipts