-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Autosave failed; log full of "Forbidden" warnings; no indication in console #4508
Comments
Just to answer part of my final question above: it looks like in the first instance "Forbidden" precedes "403 PUT", so the former is not a response to the latter. |
Cookies being revoked or expiring could cause this. If you open a new tab and login to the notebook server, you should be able to set a new cookie, which will then be used by subsequent saves in the first tab. |
OK, is there an issue for that behavior already? (Note: I accidentally closed this issue a minute ago, then reopened) |
Variables remained intact, however keep in mind that if you are in the middle of a training and you do this, that training will not continue in the new tab and when you "continue" training in the new tab, optimizer's momentum will be restarted and that could ruin the smoothness of training. |
How to fix this issue in google chrome |
We still occasionally come across this problem even on github with the latest version. |
I have just lost 2 days of code development work in a large-ish Jupyter notebook running on my laptop due to an unnoticed failure to autosave. I do not know how to reproduce this issue, but I will describe what happened and provide log output in the hopes this can lead to some resolution for this kind of issue. I am using jupyter notebook 5.5.0 on Mac OS 10.13.6 with python 3.6.8.
I typically close the laptop (put to sleep) and resume work in my Jupyter notebooks without a problem. But today I woke my laptop and noticed that the notebook was not executing new cells. I attempted to reconnect to the Kernel > Reconnect menu item. This failed, and the console indicated it would continue trying. I tried this a few times. Next (and this was the fatal step toward losing my coding work, I believe), I did ctl-r (refresh) in my browser to try to reinitiate a connection to the kernel. I was asked to enter a token. I found the token in my terminal log and entered it. When the notebook loaded, it was a version 2 days old. I verified in the terminal that notebook file was last modified 2 days ago. My work was lost.
Attached is the notebook log around the timeframe of the problem. To summarize, the output went like this, starting from a point where I woke the laptop and began working normally in the notebook:
I believe the various
Couldn't authenticate WebSocket connection
are my attempts to reconnect the kernel, and[I 11:33:39.962 NotebookApp] 302 GET notebooks/TESS%20DR1%20Activity.ipynb (::1) 5.18ms
is my ctl-r refresh of the webpage that ultimately lost my code.I did not notice any warning is the notebook status area about the failure to autosave. If the underlying issue causing this autosave failure cannot be identified, it would be good to improve the monitoring of the autosave procedure to give a serious and visible warning to the user when autosave is not functioning.
A question: what can cause the (not very helpful) log warning "Forbidden"? Is it a response for the above http PUT, or something else?
The text was updated successfully, but these errors were encountered: