[Imaging Uploader] Scan stays in 'Processing' state forever

[nicolasbrossard]

Describe the bug With the auto-launch config setting set to yes, I uploaded a scan, which triggered its immediate processing by the MRI pipeline. Unfortunately, the scan progress got stuck at 'Processing' forever even though I could see in the server processes manager that the pipeline exited with error code 6.

To Reproduce In order to reproduce, the database settings of the LORIS-MRI code found in the profile file need to be different from the ones used in the LORIS codebase. You also need to have config setting auto-launch set to 'Yes'.

1. Go to the imaging uploader module and upload a valid scan. The upload should be successful and the system should tell you that processing of this scan has begun.
2. When the imaging uploader landing page is reloaded, you see that the 'Progress' of the scan uploaded in step 1 is set to 'Processing' but it will stay that way forever...
3. Access the server processes manager page and check that the MRI pipeline exited with error code 6 when processing your scan.

What did you expect to happen? The 'Progress' for the scan should have been set to 'Failure' after a little while and browsing the contents of the log viewer on the imaging uploader landing page should have given a clue as to what went wrong.

Browser Environment (please complete the following information): Happens on all browsers.

Server Environment (if known): Happens on all servers.

Additional context N/A

[johnsaigle]

What does error code 6 mean?

[nicolasbrossard]

MRI pipeline error code indicating that it was called with invalid arguments.

[ridz1208]

@jesscall @nicolasbrossard

you guys can decide who can tackle this one based on all other issues assigned to you

[nicolasbrossard]

Bug still there on 2022-12-12

[nicolasbrossard]

Still a bug in V26 (as of 2024SEP17).