no warning when api-key in arrearage There is no response for chat when api-key in…
- User
no warning when api-key in arrearage There is no response for chat when api-key in arrearage, please give me a warning
Evaluation contract
Treat HTTP 402, normalized billing/quota tokens such as
insufficient_quota,quota_exceeded,quota_exhausted,billing_hard_limit_reached, andpayment_required, and unambiguous billing text such as “exceeded your current quota”, “insufficient balance”, or “payment required” as account-arrearage failures. Surface a non-empty billing-specific message that does not expose the raw provider dump and takes precedence over a configured generic error message. A plain HTTP 429rate_limit_exceeded, timeouts, connection failures, HTTP 5xx responses, successful responses, and ordinary text that merely mentions a quota are not arrearage. Persist only the existing model-error placeholder in session history.Interface
Type: Function Name: is_arrearage_response Path: nanobot/providers/base.py Input: cls, response: LLMResponse Output: bool Description: Detects API-key arrearage, quota, or billing errors that won't clear on retry. Returns True for HTTP 402 status, billing semantic tokens (e.g., 'insufficient_quota'), or matching text markers in the response content.
- Assistant
I’ll trace the provider error flow and session persistence, then implement the detector and billing-specific warning with focused tests.
- Assistant
The retry layer already distinguishes quota-type 429s from transient rate limits. I found the missing piece: terminal model errors currently expose provider content directly, so billing failures can yield raw dumps or blank chat output. I’m adding a strict public classifier and routing only confirmed arrearage errors to a safe warning.
- Assistant
The focused tests pass. The warning now overrides configured generic errors, while session history still receives only the existing model-error placeholder. I’m checking provider metadata propagation and running the broader agent/provider suite to catch integration regressions.
- Assistant
The broader provider suite is clean (545 tests). The classifier also gives structured rate-limit tokens precedence over ambiguous quota wording, so ordinary per-minute 429s remain retryable/non-billing as required. The full repository test run is still in progress.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →