Skip to content
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

protocol issue with 5.x protocol of Jupyter #11

Closed
apatrida opened this issue Apr 7, 2017 · 1 comment
Closed

protocol issue with 5.x protocol of Jupyter #11

apatrida opened this issue Apr 7, 2017 · 1 comment
Assignees

Comments

@apatrida
Copy link
Contributor

apatrida commented Apr 7, 2017

After seeing this does not work with Jupyter labs newest version, because of:

Ah, the issue is that we are expecting an idle status after every iopub message per the 5.0 spec: "Changed in version 5.0: Busy and idle messages should be sent before/after handling every request, not just execution." The classic notebook is more lenient because it also supports older protocol versions.

http://jupyter-client.readthedocs.io/en/latest/messaging.html#kernel-status

@nikitinas
Copy link
Contributor

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants