The Elixir Livebooks don’t work properly. Even when auto saving is enabled, sometimes it’s not saved. I just lost several hours of work. Again!
Whoah that’s no good. When you say “not saved”, do you mean that changes vanish after a refresh? Or are things disappearing between sessions?
Will you check the logs for your livebook app? You can do this through our UI. It’s possible the Livebook process is running out of memory and crashing, which would lose state. You’ll see log messages that mention
OOM if that’s the case.
Dang, losing work like that is so painful! Sorry to hear that!
I tried several things but I’m not able reproduce this. Can you provide any more information? I’ve run Elixir scripts that intentionally crash the Livebook instance and it still keeps my files.
It’s worth noting that the default location where files are stored is on the “Local Disk”. When running this on Fly.io, it means it’s running on a VM. It’s not guaranteed to be persistent storage.
Livebook offers a persistent storage option. Are you using that?
You can add an AWS S3 compatible storage location. The page also links to Storj which is S3 compatible and has free options.
I hope that helps!
@Josef_Richter I was wrong!
When the Livebook instance is created, a persistent volume is also created and mounted as
/data. That’s where the notebook files are written.
So you do still have the option of external storage, but if you keep it in Livebook on Fly it should work. Even stopping and starting the instance on Fly kept my file.
If you have any additional info or steps to reproduce, I’m happy to look at it again!