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

Spurious "another browser tab is already connected to the kernel" #42

Closed
ravwojdyla opened this issue Oct 2, 2024 · 2 comments
Closed

Comments

@ravwojdyla
Copy link

Spurious "another browser tab is already connected to the kernel". #41 is great improvement! In the latest version I still experience spurious "another browser tab is already connected to the kernel" errors:

image

Initially the notebook worked fine, then after browsing a couple of source code files, and reopening the notebook I would see the error above. Then after some time and a couple of closing and reopening of the notebook it worked again:

image

@mscolnick
Copy link
Contributor

Thanks for pointing this out - we must still be holding onto a websocket connection still. I'll investigate

@mscolnick
Copy link
Contributor

Going to close this since we now allow "taking control" when there is another tab connected.

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

2 participants