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

Request for help in interpreting a diagnostic message from ipywidgets (KeyError) #2163

Closed
mprogram opened this issue Aug 2, 2018 · 6 comments
Labels
resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@mprogram
Copy link
Contributor

mprogram commented Aug 2, 2018

It's rather a question, not an issue:

With the help of kernelspy upon running various examples (animations in pythreejs, etc., namely, when rendering a core functional part of a corresponding widget)* I'm getting this kind of a diagnostic message:

0: "---------------------------------------------------------------------------"
1: "KeyError Traceback (most recent call last)"
2: "/usr/lib/python3/dist-packages/ipywidgets/widgets/widget.py in _handle_msg(self, msg) 660 """Called when a msg is received from the front-end""" 661 data = msg['content']['data'] --> 662 method = data['method'] 663 664 if method == 'update': "
3: "KeyError: 'method'"

How should I interpret it in simple terms? Thank you in advance.
*. JupyterLab 0.33.6 and ipywidgets 7.3.1

@jasongrout jasongrout added this to the Reference milestone Aug 2, 2018
@jasongrout
Copy link
Member

Do you have a simple self-contained example reproducing the issue?

@jasongrout
Copy link
Member

It seems that the kernel side is not getting a correctly-formed message from the javascript.

@mprogram
Copy link
Contributor Author

mprogram commented Aug 2, 2018

Yes, it's a continuation of issue(s) no. 206 on pythreejs, nos. 14 and 13 on ipywebrtc, and no 159 on ipyvolume. I've seen a similar message referenced by me in pull request no. 661 on bqplot.

@mprogram
Copy link
Contributor Author

mprogram commented Aug 3, 2018

I've just posted a detailed investigation on the pythree issues. Please, have a look there.

@mprogram
Copy link
Contributor Author

mprogram commented Sep 4, 2018

No longer the issue after various upgrades, closing.

@mprogram mprogram closed this as completed Sep 4, 2018
@jasongrout
Copy link
Member

Great, thanks for following up here. I'm glad it's working for you now.

@lock lock bot added the resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label May 21, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

No branches or pull requests

2 participants