Random ECONNREFUSED errors are popping up in the wild #3599
Comments
|
I personally am getting this on my home machine. |
|
Not sure if you've checked in any code that attempts to fix it, but updating to latest dev build didn't fix the problem. |
|
I'm not going to fix this now as we have no repro. Just adding more logging. |
rchiodo
referenced
this issue
in microsoft/vscode-python
Mar 7, 2019
For #4573, #4497
Add more logging around server death and connection problems. Make kernel spec connection problems not cause server crash
Also adjust the version of 'ws' in use.
<!--
If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.:
- [x] ~Has unit tests & system/integration tests~
-->
- [ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
- [x] Title summarizes what is changing
- [x] Has a [news entry](https://github.com/Microsoft/vscode-python/tree/master/news) file (remember to thank yourself!)
- [ ] Has sufficient logging.
- [ ] Has telemetry for enhancements.
- [ ] Unit tests & system/integration tests are added/updated
- [ ] [Test plan](https://github.com/Microsoft/vscode-python/blob/master/.github/test_plan.md) is updated as appropriate
- [x] [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package-lock.json) has been regenerated by running `npm install` (if dependencies have changed)
- [ ] The wiki is updated with any design decisions/details.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Number of issues reported with this:
microsoft/vscode-python#4413 is one example.
We need more logging around ECONNREFUSED. Or perhaps Jupyter Server crashing.
The text was updated successfully, but these errors were encountered: