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

'AsyncIOLoopKernelManager' object has no attribute 'ports_changed' #1086

Closed
fcollonval opened this issue Nov 23, 2022 · 3 comments · Fixed by #1088
Closed

'AsyncIOLoopKernelManager' object has no attribute 'ports_changed' #1086

fcollonval opened this issue Nov 23, 2022 · 3 comments · Fixed by #1088
Labels

Comments

@fcollonval
Copy link
Member

fcollonval commented Nov 23, 2022

Description

#1047 introduces a new assumption on the KernelManager API that is not correct kernel_manager.ports_changed is not mandatory (it does not exist on the abstract class nor on the default jupyter_client.ioloop.AsyncIOLoopKernelManager) :

if self.kernel_manager.ports_changed(self.kernel_id):

Reproduce

Error seen on JupyterLab CI: https://github.com/jupyterlab/jupyterlab/actions/runs/3530210941/jobs/5921960684

Expected behavior

No error

Reference

Version: jupyter_server-2.0.0rc6

@fcollonval fcollonval added the bug label Nov 23, 2022
@fcollonval
Copy link
Member Author

The call existed in the code prior to #1047 in jupyter_server/services/kernels/handlers.py#L464

@Zsailer
Copy link
Member

Zsailer commented Nov 23, 2022

Thanks, @fcollonval. Looks like #1047 calls ports_changed at the wrong level.

This has been an annoying readability issue in Jupyter Server for a long time. When JS says kernel_manager is usually means the Mapping/Multi Kernel Manager, not the individual Kernel Managers. in #1047, I tried to be more explicit, but looks like I got it wrong in this instance.

@fcollonval
Copy link
Member Author

Thanks @Zsailer for the quick fix and thanks @blink1073 for the new release

Happy Thanksgiving to both of you

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

Successfully merging a pull request may close this issue.

2 participants