I am running seafile 13 with the new seadoc 3.0.2-testing, but this also appeared with 2.xx
Whenever my websocket operation from exaclidraw exceeds 200, a warning is thrown onto my UI.
In the console I read the following error:
https:// pastebin .com/4VAF5QCg
How to fix, is it a bug, or am I stupid?
Thanks in advance?
seadoc 3.0.2-testing is for seafile 14 (not released yet). You should use seadoc 2.0 version to work with seafile 13.
Ofc, but I switched from 2.xx to 3. testing because of that error. In order to test if it persists and it does
@daniel.pan still here?
What do you mean by “exceeds 200”?
Do you mean you performed more than 200 operations, then the software will produce an error? We cannot reproduce the behaviour in our daily working with Excalidraw.
@daniel.pan
Whenever it exceeds some kind of threshold, it starts. As the server keeps the changes I suppose something might be wrong with clearing the queue after the changes have been send. As seen in the screenshot, the server answers with success, but the issue still persists
Okay, seems like a bug. We will give it check soon.
We have not found obvious bug in the code. Can you reproduce the issue on plus.seafile.com?
I just registered and checked. The issue is reproducable. Just hold down, draw and then the error keeps spamming.
What do you mean by “hold down”?
Holding down the button to draw:
I have recorded a video. The issue starts at 18 seconds (which is longer than on my instance), but still persists. I’ll send you a private message to the video.
Thanks.
The problem is caused by that the client can not send operations to server fast enough.
We will see how we can improve the algorithm.
@daniel.pan thanks for looking into it. The issue I have is, that this warning is persistent and wont go away, aber it has been triggered
