We recently installed Prodigy on an Ubuntu Server 18.04 VM. We have been running on Windows without issue but wanted to be able to leverage some of the command line tools which only have coloring on Linux.
However, we have lost almost all of our work that was done on this instance of Prodigy. 1 or 2 documents were successfully saved, but in the other sessions although it claimed to save successfully, when we relaunched Prodigy the total count was back to the original number (plus 1 or 2). I would have thought it might be an issue with the location of our DB file, but the fact that several documents were successfully saved seems to rule that out. Nothing was logged in the command window. I am not sure what to look at next, please advise.
Also, a second question which might be a pip/Python issue rather than a Prodigy issue, but we are seeing some pathological behavior with the dependencies. "sudo pip3 list" is showing that srsly is installed for me, but the exact same command for another developer does not include it, and so she is unable to start Prodigy on that server at all. We verified that it's using the same pip with "sudo which pip3." Is there anything we can look at to see why this would be the case? We haven't had any issues like this on Windows.