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.

Sign up for GitHub

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

Jump to bottom

Unit test connection and connection restoration after failure #20

Open

1 of 3 tasks

krassowski opened this issue Sep 5, 2019 · 0 comments

Open

1 of 3 tasks

Unit test connection and connection restoration after failure #20

krassowski opened this issue Sep 5, 2019 · 0 comments

Milestone

Member

krassowski commented Sep 5, 2019 •

edited

Loading

Follow up on #4. Two major scenarios to test:

LSP server not available when notebook starting, but available afterwards
connection to the LSP server temporarily lost

Also:

the LSP server encounters a serious error and the pipe gets broken; it should be restarted; we should require that no more that 3 failures occur or that they occur not more often than once every 15 minutes.

krassowski added this to the 0.6 milestone

krassowski modified the milestones: 0.6, 0.8

krassowski modified the milestones: 0.8, Future

krassowski mentioned this issue

[WIP] Ensure recovery from BrokenPipeError #563

Open

4 tasks

doodleEsc mentioned this issue

Broken pipe error and test drive report #274

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment