Skip to content

fix: prevent transient upstream failures from cascading into cooldown 429s - #999

Merged
chenyme merged 1 commit into
mainfrom
build
Aug 24, 2026
Merged

fix: prevent transient upstream failures from cascading into cooldown 429s#999
chenyme merged 1 commit into
mainfrom
build

Conversation

@chenyme

@chenyme chenyme commented Aug 24, 2026

Copy link
Copy Markdown
Owner

fix: prevent transient upstream failures from cascading into cooldown 429s

  • enable HTTP/2 health checks for all Grok Build transports
  • evict idle Build connections before upstream idle timeouts
  • apply the transport policy to direct, proxy, SOCKS, and tunnel clients
  • treat non-account-scoped upstream 5xx responses as short soft cooldowns
  • preserve HTTP status diagnostics without increasing persistent failure counts
  • keep genuine 429 handling and Retry-After behavior unchanged
  • add coverage for HTTP/2 transport settings, soft cooldowns, and account rotation

@chenyme
chenyme merged commit 316f3ba into main Aug 24, 2026
9 checks passed
@chenyme
chenyme deleted the build branch August 25, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Sub2API 原生 Grok OAuth 正常,但 OpenAI-compatible bridge 持续返回 429

1 participant