-
Notifications
You must be signed in to change notification settings - Fork 8
Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer #74
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 #74
Comments
I am having the same problem. Set up seems to be going fine, user is fetched properly, connecting to the kernel looks fine, but executing a cell never ends, no debug info is shown or logged except some
|
@alastairtree @hnykda lets use this issue going forward, as i think this is slightly different though the symptoms are the same. |
I'm sorry you are running into this issue. |
Thanks! |
@alastairtree @hnykda @hermaneyd Here's the vsix, please install this and let me know how it goes. Please could you
|
@DonJayamanne, after installation your vsix in VS Code Insiders I got an extensions host termination. I tried to find any logs but to no avail =( Bisect points out that ms-toolsai.jupyter extension cause it.The same crash I observed with ms-toolsai.jupyter v2024.11.0. By the way v2024.10.0 doesn't have this problem (extensions host termination). |
@hermaneyd Sorry you ran into that issue, please can you try this new VSIX |
@DonJayamanne, the problem still remains – host terminated unexpectedly during kernel detection
|
After installing the new VSIX, I lost connection to the server. |
Hi @DonJayamanne! I am also seeing this issue. Any progress on this? Running into this on version ms-toolsai.jupyter:2025.2.0, windows 11. I am not using jupyterhub. I was directed here when looking through similar issues to this in the vscode-jupyter repo. What is the cause of this issue? |
I've "fixed" the It seems the event data is a nodeJS Buffer where it's supposed to be a string. Tested by editing I hope this helps someone find the root cause and make a proper fix. |
@MMM-J Thank you for your investigation, I'm struggling to understand the code change. @MMM-J Please can you check the next comment, would love some help with the logs to get a proper fix (your fix does seem to work, but I'd like to understand whats going on and why). |
Please can someone test the following vsix(s)
ms-toolsai.jupyter.2025.4.0.alpine-arm64.vsix.zip |
@DonJayamanne hi, I've tried your VSIX
|
@timonovid Thank you for the logs. |
@timonovid I have updated the VSIX with some more logging |
@DonJayamanne Thank you for the updated VSIX. Unfortunately the problem is very difficult to reproduce. Currently only one user is experiencing it, and I’m unable to reproduce it on my own instance. Logs from the new VSIX are below:
|
Installed
|
Please can you reopen #67 because the issue still remains when connecting to a JupyterLab server Version 0.35.5, even when using the latest pre-release versions of Jupyter and JupyterHub vscode extensions. As mentions, reverting to previous versions fixes the issue.
The text was updated successfully, but these errors were encountered: