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

Server/client should find an available port rather than erroring #64

Closed
itsdouges opened this issue Jun 4, 2023 · 0 comments
Closed
Labels
Bug Something isn't working Chore

Comments

@itsdouges
Copy link
Collaborator

Currently when starting the client/server it will throw an exception if the port it wants to listen on is already used. This issue should:

  • add ability to find a free port
  • refactor editor to be told what port to use
@itsdouges itsdouges added the Chore label Jun 4, 2023
@itsdouges itsdouges added this to the Milestone 4 milestone Jun 4, 2023
@itsdouges itsdouges self-assigned this Jun 7, 2023
@itsdouges itsdouges added the Bug Something isn't working label Jun 7, 2023
@itsdouges itsdouges removed their assignment Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Chore
Projects
None yet
Development

No branches or pull requests

1 participant