Skip to content

fix(pool): bound account hops and stop on repeated bare 429s - #1165

Merged
dofastted merged 9 commits into
mainfrom
fix/pool-bare-429-account-cap
Nov 16, 2026
Merged

dofastted merged 9 commits into
mainfrom
fix/pool-bare-429-account-cap

Conversation

@dofastted

@dofastted dofastted commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

替代 #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_request so a single request stops hopping to new accounts once enough executed accounts are reached; admission failures like slot_busy do 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_request instead of cooling accounts or Fable and keeps spreading.

rate_limited_request is 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.

@cursor

cursor Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot 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)

@dofastted
dofastted changed the base branch from fix/panel-pr1160-followups to main November 16, 2026 21:54
@cursor

cursor Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot 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)

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.

1 participant