Repository navigation
2026.10.26: upstream throttling and usage limits; pin core v0.79.0 - #352
Merged
Merged
Conversation
- Upstream dialog: Usage limits under the concurrency limit, reusing the key limits editor; minute and hour periods take "every N". Gateway keys get every N too. Share links and exports carry the limits. - Settings > Failover: "Wait at most" (failover.wait_secs, default 120 s) replaces the free-slot wait. - Upstreams page: a live countdown tag while an upstream is rate limited or at a usage limit, and each limit's usage on hover. - Traffic: queued requests show what they wait for until request_dequeued; the route view shows 429 pauses and the new skip reasons. - zh for the new core message codes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
failover.wait_secs, default 120 s) replaces the free-slot wait. The Upstreams page shows a countdown tag while an upstream is rate limited or at a usage limit; Traffic shows queued requests (untilrequest_dequeued) and the route view shows 429 pauses and the new skip reasons. zh for the new core message codes.Upgrade notes
A configuration that set
failover.slot_wait_secsopens in safe mode after the upgrade; the repair removes it. The Lite settings page only writes failover fields that were changed, so configurations that never changed "Wait for a free slot at most" are unaffected.Testing
Locally against a twcore built from v0.79.0: typecheck, vitest (1288), cargo fmt/clippy, cargo test (965).
🤖 Generated with Claude Code