You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of expected behavior and the observed behavior
A few days ago the below example was working fine for me, I could see the print and/or logging.info messages in the VSCode Jupyter Window. Now messages printed during __init__ still work, but when I print messages during an event callback, the messages don't appear in the Jupyter Window anymore (see the video below).
In the Jupyter Console I'm seeing the following messages:
Unhandled kernel message from a widget: stream : {"name":"stderr","text":"INFO:root:Clicked 1 times.\n"}
Complete, minimal, self-contained example code that reproduces the issue
Just downgraded to VSCode == 1.96.4 and things are back to normal. As in: the messages now show up in the Jupyter Window. I do still see those Unhandled kernel message from a widget: stream : messages as well though...
Now I don't know if this is a "bug" on holoviz side or not.
ALL software version info
(this library, plus any other relevant software, e.g. bokeh, python, notebook, OS, browser, etc should be added within the dropdown below.)
Software Version Info
Python env created with conda from conda-forge.
Description of expected behavior and the observed behavior
A few days ago the below example was working fine for me, I could see the print and/or logging.info messages in the VSCode Jupyter Window. Now messages printed during
__init__
still work, but when I print messages during an event callback, the messages don't appear in the Jupyter Window anymore (see the video below).In the Jupyter Console I'm seeing the following messages:
Unhandled kernel message from a widget: stream : {"name":"stderr","text":"INFO:root:Clicked 1 times.\n"}
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
Screen.Recording.2025-02-11.at.09.36.47.mov
The text was updated successfully, but these errors were encountered: