You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have several reports in the Uploads table that have status = "IN TREATMENT" and message = "The document has been uploaded successfully". Looking at upload_reports_job() this shouldn't be possible, as that message is only set if the status is simultaneously set to "TREATED".
To Reproduce
I believe that what has happened is
Too many reports were added to the uploads/ directory.
The scheduler job (job 1) starts processing these reports.
Before job 1 is done, a second scheduler job (job 2) begins that tries to process some of the same reports that are still listed as "NOT TREATED", because job 1 hasn't gotten to them yet.
One of the jobs processes a report, sets it to status="TREATED" and message="The document has been uploaded successfully", and then deletes the file before the other job gets to it.
When the other job gets to the same report, it updates the row to "IN TREATMENT" again, and then crashes when it tries to load the file to determine gzipped status, because the file doesn't exit anymore.
Expected behavior
The reports should not show up as pending reports with "IN TREATMENT" status, but rather should be "TREATED".
System Details
SQL database: postgres
MegaQC: v0.3.0
The text was updated successfully, but these errors were encountered:
Describe the bug
I have several reports in the Uploads table that have
status = "IN TREATMENT"
andmessage = "The document has been uploaded successfully"
. Looking at upload_reports_job() this shouldn't be possible, as that message is only set if thestatus
is simultaneously set to"TREATED"
.To Reproduce
I believe that what has happened is
uploads/
directory."NOT TREATED"
, because job 1 hasn't gotten to them yet.status="TREATED"
andmessage="The document has been uploaded successfully"
, and then deletes the file before the other job gets to it."IN TREATMENT"
again, and then crashes when it tries to load the file to determine gzipped status, because the file doesn't exit anymore.Expected behavior
The reports should not show up as pending reports with
"IN TREATMENT"
status, but rather should be"TREATED"
.System Details
The text was updated successfully, but these errors were encountered: