fix: make scheduler lock port configurable with automatic fallback#333
Open
Kailigithub wants to merge 1 commit into
Open
fix: make scheduler lock port configurable with automatic fallback#333Kailigithub wants to merge 1 commit into
Kailigithub wants to merge 1 commit into
Conversation
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.
Summary
On Windows, the scheduler's hardcoded lock port
45762can conflict with the system's dynamic port range, causingWinError 10013and preventing startup.Changes
SCHEDULER_LOCK_PORTenvironment variable (default: 45762)RuntimeErrorif no port in the range can be boundRoot Cause
reflect/scheduler.pyhardcoded45762for the lock socket. On Windows, if the dynamic port range (configurable vianetsh) overlaps with this port, thebind()call fails withWinError 10013.Testing
SCHEDULER_LOCK_PORTenvironment variable override worksCloses #331