automatic-ripping-machine: 🐛 Failed to update database with associated drive

Is there an existing issue for this?

• I have searched the existing issues

I have checked the wiki

• I have searched the wiki for this problem

Does this issue exist in the latest version?

• I’m using the latest release

Describe the bug?

Inserted two DVDs at the same time and one began correctly the other failed with the error, “Failed to update the database with the associated drive” log file copy pasta’ed. This will hang the drive and is no longer able to rip.

To Reproduce

1. Insert two DVDs at the same time
2. First will begin ripping
3. Second disc will fail/hang
4. Attempting to “Abandon Job” will fail
5. Navigate to “Database”
6. Select “Delete Job”
7. proceed with ripping/attempt ripping same DVD

What OS are you seeing the problem on?

Other (please state in Anything else? section)

ARM Release Version or Git hash (You can find this in the arm settings page)

From “Arm Settings”, “General Info” Python version: 3.8.10 A.R.M version: 2.6.40 Current git version: 06e4fb1790c8fd698e2257a87b18668d4d7616c6

Expected behavior?

Both should start ripping at the same time.

Relevant log output

[07-05-2023 23:16:29] DEBUG ARM: utils.check_db_version Head is: 2e0dc31fcb2e
[07-05-2023 23:16:29] DEBUG ARM: utils.check_db_version Database version is: 2e0dc31fcb2e
[07-05-2023 23:16:29] INFO ARM: utils.check_db_version Database is up to date
[07-05-2023 23:16:30] DEBUG ARM: utils.database_adder Trying to add User
[07-05-2023 23:16:30] DEBUG ARM: utils.database_adder successfully written User to the database
[07-05-2023 23:16:30] INFO ARM: main.<module> ************* Starting ARM processing at 2023-07-05 23:16:30.123783 *************
[07-05-2023 23:16:30] DEBUG ARM: utils.database_adder Trying to add Job
[07-05-2023 23:16:30] DEBUG ARM: utils.database_adder successfully written Job to the database
[07-05-2023 23:16:31] DEBUG ARM: DriveUtils.update_drive_job Updating drive [/dev/sr0] current job, with id [27]
[07-05-2023 23:16:36] ERROR ARM: DriveUtils.update_drive_job Failed to update the database with the associated drive. (sqlite3.OperationalError) database is locked
[SQL: UPDATE system_drives SET job_id_current=? WHERE system_drives.drive_id = ?]
[parameters: (27, 1)]
(Background on this error at: https://sqlalche.me/e/14/e3q8)

Anything else?

Using the docker container version of ARM

Code of Conduct

• I agree to follow this project’s Code of Conduct