fix: Pip servers handle config changes gracefully #142
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.
Testing
I used a configuration targetting the first few ports starting at
10000
Initial config (servers all commented out)
Pip server port becomes reserved via config change
10000
)"http://localhost:10000/"
localhost:10000
should be listed under "Stopped" and no longer under "Managed"Start server outside of extension
10000
(outside of extension)Arbitrary config change
resolves #137