Sensible crash recovery during book loading
I usually load books into my Kobo in fairly large batches. For example, I just loaded almost the entire Baen Free Library, 97 works.
The Kobo has helpfully decided to crash and reboot early in the process of scanning the new books to add them to the database. Which book is causing problems? WHO FRIGGING KNOWS. It doesn't report which book it's processing on the display, nor does nickel even log it to stderr where I could capture it by redirecting stderr to the sd card.
It certainly doesn't do anything as useful as checkpointing its progress so that the startup code can tell the difference between a normal startup and "nickel crashed while scanning books and needs to be re-started after skipping problem book (x)".
That leads me to my feature request: Checkpoint progress while loading books. If nickel crashes while loading one, skip to the next book, record the problem, and tell the user about it at next startup. Even better, load each book in a child process, so you can just wait() for it and check the exit code to see if it succeeded or crashed.
|