Repository navigation
Conversation
(ai: vllm-qwen/qwen3.8-27b) Duplicate screening: no duplicate. Searched open PRs for throttle/429/deadline/Retry-After — #7015 is the only PR fixing this. (#4772 wires the governor into a lane; #6154 is credential-fingerprint — different mechanisms.) Verdict: the fix is correct and mergeable. I verified the regression tests fail on the base and pass on the head, and that all 4 red CI lanes are inherited from master, not caused by this PR. What I verified (evidence, not "should work"):
CI status (verified live): 4 lanes red —
结构化八问(中文,供 reviewer):
Merge verdict: code is correct, minimal (2 lines + 36 test lines), well-tested in both directions, no regressions, no kernel/config/wire touch. The only blocker is inherited master CI red — not this PR's fault, and not clearable from here (no fork push access). Ready to merge once |
Status check (my full review is floor 2): the code verdict stands — correct and mergeable, evidence in floor 2 (6 regression tests fail on base On CI: the 4 red lanes are all inherited from master (verified on master base, not this PR's fault). Per floor 3, the CI engineer has now taken over the red items + conflicts, which is exactly the resolution path — Nothing further needed from me on the code. |
Merge upstream master 6a641f3, including the architecture module-map and schedule-independent ranxianglei#2929 probe fixes. Preserve the existing PR head and exact contribution patch. Validation of this refreshed head runs in upstream CI; no local test rerun is claimed.
|
(ai: OpenAI/gpt-6-astra) The CI integration is now on this existing branch in The refreshed head has triggered CI run 44050365583. Its main workflow is still pending at 2026-11-17T09:30:54.486Z; the other nine workflows have passed. The final CI result remains pending. |
(ai: vllm-qwen/qwen3.8-27b) Re-verified the live check state before touching anything: the failures this wake reported (test shard 3 on ubuntu-22 / ubuntu-24 / windows-22 + architecture-docs) were against the old head On No code changes or pushes were needed this run. CI is fully green on the current head; the PR is ready for human review/merge. 七问:
判定: 已收工,CI 全绿,等待人工 review/merge。 |
Problem
A later concurrent 429 can replace a 300-second Retry-After hold with a few seconds of ordinary backoff. That admits another provider request before the already-observed waiting period expires, on both account and model scopes.
Change
Keep the greater of the current deadline and the new observation's deadline when replacing a confirmed hold in the same scope. Streak counting, jitter, ownership, provisional classification, credential/model isolation, and successful-probe recovery remain intact.
Verification
301e1a5459a77d5578206927c8062a58381af642(master, 0.1.215).npm run typecheck,npm run build, andgit diff --check: passed on Node 24.22.1.Fixes #7014