Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Handle kernel status #76

Closed
jtpio opened this issue Oct 21, 2019 · 2 comments · Fixed by #304
Closed

Handle kernel status #76

jtpio opened this issue Oct 21, 2019 · 2 comments · Fixed by #304
Assignees
@jtpio
Milestone
0.1.0

Comments

@jtpio
Copy link
Member

jtpio commented Oct 21, 2019

For now we don't check whether a kernel is ready before sending debug messages.

We should do that check before starting a new session and restoring an existing one. And also handle status changes.
@jtpio jtpio mentioned this issue Oct 21, 2019
Merged
@jtpio jtpio self-assigned this Oct 21, 2019
@jtpio
Copy link
Member Author

jtpio commented Oct 21, 2019

Looking into that one.

@jtpio jtpio mentioned this issue Oct 22, 2019
Merged
@jtpio jtpio mentioned this issue Oct 30, 2019
Merged
@jtpio jtpio added this to the Future milestone Nov 5, 2019
@jtpio
Copy link
Member Author

jtpio commented Nov 11, 2019

We should also handle the case when switching to a kernel that does not support debugging (for example from xeus-python to ipykernel).

In that case the debugger UI will have to be removed (or at least disabled).

@jtpio jtpio modified the milestones: Future, 0.1.0 Dec 11, 2019
This was referenced Dec 11, 2019
Merged
Merged
Closed
Closed
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jtpio jtpio

Labels
None yet
Projects
None yet
Milestone
0.1.0
Development

Successfully merging a pull request may close this issue.

Handle kernel restarts jtpio/debugger
Handle kernel restarts jtpio/debugger
1 participant
@jtpio