fix(windows): robust daemon startup and port discovery #314
+97
−32
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
- Start daemon via PowerShell Start-Process to avoid Windows path/escaping issues - Strip \\\?\ prefix to prevent Windows dialog errors - Allow daemon to fall back to an OS-assigned port and persist it to a .port file - Read the .port file on the CLI to connect to the correct session port - Increase TCP readiness timeouts on Windows
Contributor
|
Someone is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
feketegabor
force-pushed
the
fix/windows-daemon-ports
branch
from
28d2d81 to
69df523
Compare
|
wait for it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Fixes
Fixes #132
Fixes #37
Fixes #91
Fixes #89
Testing