Repository navigation
fix(pool): 保留已绑定会话的 VM 调度粘性(v1.4.129) - #1172
Merged
Merged
Conversation
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: 632d146c-7a26-4c14-9a8a-a79f21518de4) |
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.
改动
验证
Note
Medium Risk
Touches core Claude and Codex VM selection and queue wait logic used on every inference request; misbehavior could mis-route sessions or starve higher-priority VMs, though failovers and quota gates remain in place.
Overview
Bumps to v1.4.129 and documents that active Claude/Codex session bindings now win over
schedule_level, weight, and pool rebalancing—follow-up turns and queued continuations stay on the original VM when that VM is still schedulable, instead of hopping to a newly favored account.Claude (
pool-scheduler.mjs): sticky resolution runs before priority filtering inpick,peekAccount, seat opening, and sticky seat waits; changing another VM’s priority no longer promotes a waiter off its pinned home.session_affinity_firstis narrowed to post–slot_busyspill follow-through, not whether sticky beats priority (that is now default). Codex (openai-account-selector.mjs,codex-slot-pool.mjs): preferred/bound account is chosen first, withoutpreferredOverridesWeightor a priority/weight gate.Quota drain, hard unschedulable failover, sticky wait timeouts, and outbound session identity rules are unchanged. Unit tests are updated to lock in the new ordering.
Reviewed by Cursor Bugbot for commit 4fd40e3. Configure here.