AI API receipt · sgl-project/sglang

PoolsideV1Detector silently retypes nullable/union string arguments

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

✓ Badgr rejects this response

A ["string","null"] argument "123" came back as the integer 123.

Outcome contract verdict: tool call arguments do not match the tool schema. 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.

tool_calls: [{"type": "function", "function": {"name": "lookup", "arguments": "{\"zip\": 123}"}}]
tools: ["lookup"]
tool_choice: "required"

Badgr receipt

Written by Badgr’s receipt ledger and read back from GET /v1/receipts/replay-sglang-43149-nullable-string.

{
  "request_id": "replay-sglang-43149-nullable-string",
  "status": "failed",
  "endpoint": "/v1/chat/completions",
  "stream": false,
  "failure_stage": "outcome_contract",
  "error_code": "invalid_outcome",
  "error_message": "Response did not satisfy the outcome contract: tool call arguments do not match the tool schema",
  "retryable": true,
  "provider_mode": "replay",
  "routing_decision": "replayed_upstream_output",
  "created_at": "2026-10-09T02:14:36Z"
}

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