Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

always Port in use #9717

Open
1 task done
Vineetchelani1304 opened this issue Jan 17, 2025 · 2 comments
Open
1 task done

always Port in use #9717

Vineetchelani1304 opened this issue Jan 17, 2025 · 2 comments
Labels
kind: bug Something isn't working needs: author input

Comments

@Vineetchelani1304
Copy link

Verify canary release

  • I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/Vineetchelani1304/excelidraw

Which canary version will you have in your reproduction?

[email protected]

Enviroment information

PS D:\Cohort\excalidraw> npm list turbo
excalidraw@ D:\Cohort\excalidraw
└── [email protected]

Expected behavior

must release the the port when not in use

Actual behavior

again and again getting the same messgae even when the port is not in use.
using the command taskkill /PID portId /F
i am killing the ports
please help me out i am stuck in this loop not able to check mu code
Image
Image
Image

Image
Image
Image
Image

To Reproduce

Image

Additional context

No response

@Vineetchelani1304 Vineetchelani1304 added kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels Jan 17, 2025
@chris-olszewski
Copy link
Member

Can you clarify how turbo is involved here?

  • Did you run turbo, exited, and a port from one of the tasks is still in use? If so, what turbo command did you run?
  • The error you show is for port 8888 being in use, but it looks like you're trying to clean up ports 3000 and 3001.

@chris-olszewski chris-olszewski added needs: author input and removed needs: triage New issues get this label. Remove it after triage labels Jan 17, 2025
@chris-olszewski
Copy link
Member

I see you're using NPM 10.0.0 which is affected by npm/cli#6684, upgrading past 10.3.0 might help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working needs: author input
Projects
None yet
Development

No branches or pull requests

2 participants