Issues with nteract

[alexarchambault]

Currently seeing plenty of issues when running the latest almond (master, but it seems to occur for 0.4.0 too) in nteract 0.14.2:

• statuses seem not be picked when the kernel starts (sometimes they do get picked after having run a few cells)
• things sent as display data (println("foo"), or var n = 2 with the current master) aren't printed straightaway. One can manage to print them by running another cell (with simpler code say, like just 2…)

[rgbkrk]

cc @captainsafia @benrussert @willingc

[captainsafia]

Thanks for opening this issue, @alexarchambault!

Do you have the permissions to move it to the nteract/nteract repo for tracking there?

[alexarchambault]

@captainsafia Seems the transfer issue dialog is buggy for me, the repo list I can transfer things to is empty most of the time. But I can always open another issue there.

I don't exclude the problem to originate from almond though. I had initially opened this issue as a reminder to investigate that in more detail here.

[rgbkrk]

I've added you to the org @alexarchambault. 😄 Whenever you've got more detail on how we should look into this, let us know. I've just jumped out of paternity leave so I'm now looking into github notifications again. 😅