-
Notifications
You must be signed in to change notification settings - Fork 42
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
infinite failure loop - emacs locked up #75
Comments
here is the full loop in
|
Eventually it dies with
|
the server logs show these messages:
apparently |
Sorry for the delay - I'll take a look at this today. |
Right now I don't have enough information to work on this issue. A few comments, though: If someone can track this down to something |
Actually, I see the infinite loop now, based on your backtrace in the other bug. When there's an issue, we aren't re-opening with the custom headers, which seems like a problem. I'm not sure if that will really fix your issue, but I'll push a fix for you to test out. |
Ok, please try branch |
Thank you very much. I can reproduce the problem quite reliably, but it requires private host access that I cannot grant you. |
No change with the |
Interesting - can you also trace calls to |
1st call:
after I hit
(incidentally, given that you are using lexical bindings, the 2nd call:
and then after Would you like to pick a time for an interactive debugging over the phone? |
Thanks for the results, but those are a little bit hard to read. I should have been more precise: can you |
here you go (I clicked on
|
Interesting, thanks. The interesting thing is that This automatic reconnect seems like a problem. I need to think a little more deeply about if this reconnect is even a good idea. In the meantime, you can try setting the function |
Actually I get two errors:
The notebook is left in a disconnected state and any attempt to reconnect results in another series of the same:
PS. Just to make it clear - |
Cool, this is good. So it looks like now, you have yourself a regular old 403 error. Why, I have no idea, but probably this isn't websocket's fault. Given the info that you've sent, I think I can rig up a reproducible case for this, which will allow me to proceed. I'll let you know when I have something else for you to test. In the meantime, you can work on the 403 error, which will probably fix the subsequent infinite loop. If it doesn't, please let me know. |
according to @dickmao, it is: tkf/emacs-request#193 (comment) |
I've removed the whole process of trying to automatically reconnect in 36deb3f, on the |
websocket-ensure-connected
triggers an infinite reconnect loop.Please see millejoh/emacs-ipython-notebook#750 for details.
I would appreciate guidance in debugging this.
Thank you!
The text was updated successfully, but these errors were encountered: