Repository navigation
fix(pool): bound account hops and stop on repeated bare 429s - #1165
Merged
Merged
Conversation
# Conflicts: # src/lib/transport/rust-kernel-supervisor.mjs
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 9629fa06-5d14-4e5b-bd04-d04eba3eedac) |
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 2f116b20-9418-4a26-a007-bc7565f9fb1c) |
This was referenced Nov 16, 2026
fix(pool): cap accounts per request, scope bare 429 by evidence, keep failed hops in debug log
#1127
Closed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
替代 #1127/#1135 中仍存在的请求扩散和错误判级问题;依赖 #1162 的请求级错误免额度探测。保留有证据的额度/RPM/Fable 冷却;裸 429 不捏造冷却,两账号同请求裸拒绝就返回原 429。可选账号硬上限只统计真正执行过的账号。复用限流探测,不记录原始失败 hop、分类器正文或 provider diagnostics,不引入跨请求命中缓存。
与 #1162 联合定向 211 项通过,未部署。待 #1162 合并后转向 main。
Note
Medium Risk
Changes failover hopping and upstream 429 handling on the hot inference path; behavior is bounded by new tests but misclassification could still affect quota spread or when requests stop retrying.
Overview
Adds
failover.max_accounts_per_requestso a single request stops hopping to new accounts once enough executed accounts are reached; admission failures likeslot_busydo not count. Panel docs describe the knob and the new bare-429 behavior.429 classification and failover are tightened: unknown/bare 429s no longer invent account cooldowns unless headers prove a future reset; Fable-family cooldown applies only when unified 7d_oi (or forwarded provider) headers prove a Fable window—not from the model name alone. If two different accounts each get an executed bare 429 on the same request, the runner stops with
rate_limited_requestinstead of cooling accounts or Fable and keeps spreading.rate_limited_requestis treated as request-stateless so VM schedule state is unchanged. Unit tests cover the two-account bare-429 stop, the account cap, and updated upstream 429 policy expectations.Reviewed by Cursor Bugbot for commit 4721eee. Configure here.