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.
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
Restart: Cleanup kernel process #877
Conversation
8b41214
to
4e7b79c
Compare
4e7b79c
to
33a7d6a
Compare
#863 is still active. |
@wowserx Just to make sure, have you tested with the latest |
I feel silly, wasn't running atom in dev mode. #863 is no longer active! It works fine. |
Awesome thanks for checking! 🎉 I'll ship a patch release since this fixes a critical issue. |
I still can reproduce with latest master v1.17.1. My steps to reproduce is
let a = [1, 2, 3]
a.push(10)
a // %%
a.push(20)
a // %%
a.push(30)
a.map(e => e * e)
a // %%
My keymap is here,
|
I can reproduce the above, but it's not the same problem as #863, since the code is definitely running, just not consistently re-populating the bubbles. In #863, the process was hanging indefinitely, but in the issue described above I've had it work where only some of the bubbles populate, but their results are correct: I could also reproduce this problem by mashing a custom keymap which calls restart kernel and clear bubbles simultaneously, then quickly running the code. |
@BenRussert Sorry for late response(I didn't noticed this comment). |
@t9md I see your issue now. This is a weird one. |
So you could reproduce it right? |
Looks like we run into #591 with IJavascript |
@t9md Is this issue something that comes up in your normal workflow, or does it only happen when you rapidly run this command? |
Yes, I can say it's easily happens in normal workflow.
This is NOT corner case of usage. |
👍 I'll take a look at it later this week. |
That sounds good to me. |
Follow up on #853
This will ensure to kill the old kernel process before starting a new one.
For me this fixes the issue describe by @t9md: #863 (comment)
Unfortunately I can't reproduce #863 so I don't know for sure if this will fix the original issue.