fix(scheduler): move singleton lock port off Windows reserved range#688
Open
winterhuan wants to merge 1 commit into
Open
fix(scheduler): move singleton lock port off Windows reserved range#688winterhuan wants to merge 1 commit into
winterhuan wants to merge 1 commit into
Conversation
45762 falls inside the WinNAT dynamically-excluded port range on some Windows machines (Hyper-V/WSL/Docker). bind() there fails with 10048 (and 10013/EACCES even with SO_REUSEADDR) despite no process holding the port, so the scheduler could never start on those hosts. Switch the lock port to 41537, which is outside the common reserved ranges. Co-Authored-By: Claude Fable 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Move the scheduler singleton-lock port from
45762to41537.Why
reflect/scheduler.pybinds127.0.0.1:45762as a singleton lock so a second scheduler instance fails to start. On some Windows machines this port falls inside a system reserved port range (Hyper-V / WSL / Docker WinNAT dynamic exclusions). When that happens:netstat,Get-NetTCPConnectionshow nothing).bind()still fails withWinError 10048.SO_REUSEADDRfails withWinError 10013(EACCES).The
10013result underSO_REUSEADDRis the tell-tale sign of a reserved range rather than an in-use port. The result is the scheduler autostart fails on every launch withOSError: [WinError 10048], even on a clean machine with no other GA instances running.Fix
Switch the lock port to
41537, which is outside the common reserved ranges, and add a comment explaining the reserved-range pitfall. Singleton-lock semantics are unchanged.Test
41537binds successfully where45762fails (10048) on the affected machine.