zyycnandClaude Opus 5 69f73e8c5d fix(xai,web): distinguish account cooldown from upstream failure ...

Selection-stage failures all collapsed into a generic "upstream service is
unavailable", so a 30s runtime cooldown was indistinguishable from a real
upstream outage. The connection test pins a single account and has no
fallback, making every retry inside the window look like a dead upstream.

Split the runtime-cooldown case out of NoEligibleSession into a new
AccountCoolingDown variant carrying the remaining wait, and attach a
structured code and error type to each selection failure. The admin
connection test now renders the reason and the remaining cooldown.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-26 22:03:42 +08:00

..

apps/gateway

chore(release): prepare v3.0.0

2026-07-25 01:54:18 +08:00

crates

fix(xai,web): distinguish account cooldown from upstream failure

2026-07-26 22:03:42 +08:00

migrations

fix(store,openai): bound dashboard concurrency and restore quota state re-read

2026-07-26 21:05:00 +08:00

Cargo.lock

perf(openai,xai): trim passive quota round trips and stream chunk copies

2026-07-26 20:35:22 +08:00

Cargo.toml

refactor(backend): finalize gateway package boundaries

2026-07-25 00:33:11 +08:00

rust-toolchain.toml

refactor: migrate backend to Rust 1.97 and edition 2024

2026-07-12 19:10:56 +08:00