-
Notifications
You must be signed in to change notification settings - Fork 6.3k
-
I want to open a big (>15M) jupyter notebook ,the get the error msg: websocket err 1009 message too big
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 3 comments 3 replies
-
🤔 I honestly don't know how you get around this. Maybe @code-asher knows?
Beta Was this translation helpful? Give feedback.
All reactions
-
Hmm this probably needs fixing upstream, I guess they need to chunk large messages or something.
Beta Was this translation helpful? Give feedback.
All reactions
-
изображение
Is this problem still not solved? My jupyter-notebook weighed 12mb and does not boot.
Beta Was this translation helpful? Give feedback.
All reactions
-
We never looked into it, I am not sure if it is a problem with code-server or VS Code, would be helpful if anyone can reproduce with Codespaces to see if it happens there as well.
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi yes, actually, I just ran code-server inside jupyter for my work.
The trick is that jupyter, namely tornado tornadoweb/tornado#3453 limits the messages that are transmitted via websockets.
And in the case of code-server, large files (for example, a large ipynb) are transmitted not in "chunks", but "whole".
i.e. 1 message consists of 10 or more megabytes at once. This is the problem.
There are two solutions:
- Make a "hole" on the tornado side in websockets - a bigger one
- Make a split of large objects into "chunks" on your side
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
@xczhanjun @MiXaiLL76 I simply overwrite the default values when building the image.
i Python is installed at /usr/local
Beta Was this translation helpful? Give feedback.