Wait for other instances #5488
HomerHaddock
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary:
I have noticed that when beets is already running any other notices report
database is locked
then exists. I understand that having two beets instances editing the database causes problems, but what is stopping beets from waiting? Software that has a database likeapt
have instances wait when the database is locked, so why not have beets do the same?Suggested change:
Have a queue for instances to wait for the database to clear up. The instance at the front of the queue is the only one to lock and change the database when the current is finished. All other instances are added to the queue and are forced to wait.
Beta Was this translation helpful? Give feedback.
All reactions