-
Notifications
You must be signed in to change notification settings - Fork 8
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
"Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer" on multiple actions #67
Comments
I just ran into the exact same issue today. Notebooks that were previously working weren't working today. Even a simple hello world. I could not execute a cell. When observing the logs, I also noticed the [error] Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer error. After a lot of troubleshooting and failing, I found that reverting the extension to version v2023.10.1003012305 solved the problem. (looks like #68 might be a duplicate) |
Same here looks like regression in newest version, reverting to version v2023.10.1003012305 solves the the problem. |
This should now be fixed in the latest pre-release version of the Jupyter extension. |
When using the pre-release, i wasn't able to connect to my server at all - so i can't confirm this fix. reverting to version v2023.10.1003012305 seems to solve the issue for me as well. |
I got the same errors when connecting to server running Version 0.35.5 of JupyterLab. Only reverting to v2023.10* versions fixed the issue. |
I think there is still an issue 😢 : #74 (comment) |
It looks like the latest version of this extension is having trouble handling WS messages from a remote JH server.
The exceptions appear in the Jupyter extension logs - but the issue seems to be caused by the latest version of this JupyterHub extension. Reverting to the previous version resolves the issue.
Environment data
Expected behaviour
Able to:
Actual behaviour
Actions never complete, and a number of Error logs are seen in Jupyter Extension logs.
Steps to reproduce:
import os
) - cell never completes running, sits with a "clock" iconLogs
Logs are from the Jupyter Extension.
The text was updated successfully, but these errors were encountered: