I upgraded to 2.11.0, found some odd errors that based on other reports came from old 2.9.0 processes still being active. So, as suggested in that thread, I stopped cryosparc, killed all python processes, and restarted. It seems that this procedure killed active database migration processes, or maybe just the notification process.
Notifications for the following were stuck with no progress:
Exporting all jobs in P6
Database Migration: Exporting all projects in cryoSPARC
I cleared the notifications, and jobs are now able to run, but I am concerned whether this may have corrupted databases. Is there a mechanism to verify databases are consistent and/or correctly upgraded?
If it is just the notification system getting stuck for incomplete jobs, maybe it should have some sort of process verification to avoid stuck notifications.
If you take a look at the Notification Manager, and check out the inactive notifications, you will probably see a “completed” notification for Database Migration: Exporting all projects in cryoSPARC. If this is there, you should be fine. The database migration does not modify the database, it just executes queries and writes out metadata to disk.
FYI, we have the same issue (notifications seem stuck in “Exporting all jobs in P9
Database Migration: Exporting all projects in cryoSPARC” state), and no “completed” notification in the Notification manager.
Restarting cryosparc did not help either.