JianFeeeee e19cff248f fix(provider): fail the candidate on error-only streams instead of serving empty replies ...

Some upstreams (zen free pool) answer HTTP 200 with a single-chunk stream
whose only payload is finish_reason:"network_error" and an empty delta.
ChatStream used to hand that channel up as a success, so clients received
a laundered empty reply (agents ended their turn mid-loop) and the broken
slot kept its scheduling preference. ChatStream now holds back the first
chunk: an error-only done chunk fails the candidate before any byte
reaches the gateway, letting the scheduler fall through to the next
source. Standard finish reasons (including instant-empty "stop") are never
classified as errors.

2026-08-24 15:41:45 +08:00

..

provider_test.go

fix(provider): fail the candidate on error-only streams instead of serving empty replies

2026-08-24 15:41:45 +08:00

provider.go

fix(provider): fail the candidate on error-only streams instead of serving empty replies

2026-08-24 15:41:45 +08:00

registry.go

fix(status): source column reflects real traffic + theme-aware tray menu

2026-08-17 17:37:04 +08:00