Lost my work because I forgot to save, and the unsaved file version wasn't up-to-date #2832
Replies: 5 comments 3 replies
-
Side note: Didn't take long to rewrite code, and I decided to store my bulky string in Tigris Storage. Using ExAWS works well. :) |
Beta Was this translation helpful? Give feedback.
-
This is unexpected. We save it every 5 seconds I believe, so the loss should have been minimal. 🤔 |
Beta Was this translation helpful? Give feedback.
-
@bgoosmanviz does the notebook use a Teams workspace? |
Beta Was this translation helpful? Give feedback.
-
Is this something you can reproduce with the same string? Formatting should definitely not crash the notebook, especially that it happens in the runtime, so if anything the runtime would crash (and that shouldn't happen either). |
Beta Was this translation helpful? Give feedback.
-
I can't repro any of this anymore. I'm not sure what sort of state (must have been quite the state!) I was in, but I am in it no longer 🤷🏻 |
Beta Was this translation helpful? Give feedback.
-
After a series of unfortunate events, I lost a few hours of work.
docker restart livebook
. Notice I didn't save the notebook 🤦🏻. Go looking in the unsaved files, find it, but the contents are out of date.Oops, my fault. The logs aren't very helpful as to how Livebook crashed in the first place.
Maybe the run command is helpful. Running on Ubuntu.
Logs show this over and over again.
Beta Was this translation helpful? Give feedback.
All reactions