Skip to content

debugger doesn't fail gracefully if port is in use #13

@boakley

Description

@boakley

If you try to run the debugger twice using the same port, the second instance crashes rather than giving a reasonable error. It should give a reasonable error such as "An instance of the debugger is already running on port xxx"

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions