fix(core): use next available port when the port for nx graph is in use #31365
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
View your CI Pipeline Execution ↗ for commit 0e74b14.
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
force-pushed
the
fix-nx-graph-port-conflict
branch
3 times, most recently
from
61b59ef to
c912529
Compare
![graphite-app[bot]](https://cdn.statically.io/img/avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
FrozenPandaz
force-pushed
the
fix-nx-graph-port-conflict
branch
from
c912529 to
827dc85
Compare
FrozenPandaz
force-pushed
the
fix-nx-graph-port-conflict
branch
from
827dc85 to
0e74b14
Compare
FrozenPandaz
changed the title
AgentEnder
approved these changes
May 29, 2025
FrozenPandaz
added a commit
that referenced
this pull request
Jun 3, 2025
…se (#31365) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> Command would fail silently with no error message ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Rather than erroring, Nx will find the next available port and use that. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #30915 (cherry picked from commit 2f37cb2)
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
Command would fail silently with no error message
Expected Behavior
Rather than erroring, Nx will find the next available port and use that.
Related Issue(s)
Fixes #30915