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

"No such comm" again #60

Open
michaelaye opened this issue May 26, 2020 · 7 comments
Open

"No such comm" again #60

michaelaye opened this issue May 26, 2020 · 7 comments
Milestone

Comments

@michaelaye
Copy link

ALL software version info

  • holoviews 1.13.2
  • notebook 6.0.3
  • Python 3.7

Description of expected behavior and the observed behavior

Not getting errors and warnings for holoviews use in a notebook.

Complete, minimal, self-contained example code that reproduces the issue

This code cell is all what one currently needs to trigger errors and warnings after a restart of the notebook:

import holoviews as hv
hv.notebook_extension('bokeh')

So, procedure to trigger the error and warning in the console is

  1. execute code cell
  2. restart notebook
  3. executing code cell again

Stack traceback and/or browser JavaScript console output

[I 13:48:32.046 NotebookApp] Replaying 7 buffered messages
[IPKernelApp] ERROR | No such comm target registered: hv-extension-comm
[IPKernelApp] WARNING | No such comm: hv-extension-comm

@philippjfr
Copy link
Member

This has been my ongoing nemesis, the warnings are definitely annoying but don't actually indicate that anything is wrong. I'll move the issue to pyviz_comms and maybe I'll finally figure it out.

@philippjfr philippjfr transferred this issue from holoviz/holoviews May 26, 2020
@michaelaye
Copy link
Author

it's intriguing though that different to the older stories, now there's also ERRORs being created.

@jlstevens
Copy link
Contributor

@philippjfr Does the suggestion that they are now ERRORs as opposed to warnings concern you or do you still think these messages are safe to ignore?

@philippjfr
Copy link
Member

No, it's really just the log level that was changed it still doesn't indicate any real error condition.

@jlstevens
Copy link
Contributor

In that case do you think this will ever be fixed (in which case this issue can stay open) or maybe this is an unfortunately case of wontfix?

@michaelaye
Copy link
Author

michaelaye commented Apr 11, 2022

aand they are back... :( (they were gone for a while...)

\[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: ad3fae9f-d861-4a71-8bf7-e466009b0650
|[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: 151ed4eb-7939-4789-aec9-552998478b1b
[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: a1f8aa4a-1358-40b4-9b34-cab7ddc665d9
[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: 6f7a646d-01ab-4f85-99a6-83d292c2429a
[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: 42dc6bd9-8e6d-48f5-8b96-498e3b88e3d5
[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: fb59eda0-c563-4360-9585-3afa6f42e1aa

@jbednar
Copy link
Member

jbednar commented Apr 11, 2022

My $500 USD bounty for anyone who can make those messages go away is still open...

@sophiamyang sophiamyang added this to the 2.2.1 milestone Aug 1, 2022
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

5 participants