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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port reported is incorrect #34

Closed
lramos15 opened this issue Jun 30, 2021 · 2 comments 路 Fixed by #40
Closed

Port reported is incorrect #34

lramos15 opened this issue Jun 30, 2021 · 2 comments 路 Fixed by #40
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@lramos15
Copy link
Member

  1. Start a process on port 3000
  2. This causes live server to go to 3001
  3. Live server shows a notification saying server started on 3001
  4. 馃悰 Server is actually on 3002

Screen Shot 2021-06-30 at 1 39 18 PM

@lramos15
Copy link
Member Author

lramos15 commented Jul 1, 2021

Can't get this dialog to appear anymore since I've uninstalled the old one. But what I do notice is this

  1. Start a process on port 3000
  2. Start live server it goes to 3001
  3. Kill the process on port 3000
  4. Kill live server
  5. Start live server
  6. 馃悰 Live server picks 3001 and doesn't reclaim 3000

@andreamah
Copy link
Contributor

Oh, this is by design so that it doesn't keep retrying ports that were occupied before each time it starts up. I thought it would be more efficient, especially if a lot of ports after the initial port are occupied. I can see that it might be unexpected, though. What do you think about this?

@andreamah andreamah added the bug Issue identified by VS Code Team member as probable bug label Jul 7, 2021
@andreamah andreamah added this to the July 2021 milestone Jul 26, 2021
@andreamah andreamah self-assigned this Jul 26, 2021
@rzhao271 rzhao271 added the verified Verification succeeded label Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants