Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Dicom Archive] When File Does Not Exist, The User Is Not Told #4558

Closed
HenriRabalais opened this issue May 13, 2019 · 14 comments
Closed

[Dicom Archive] When File Does Not Exist, The User Is Not Told #4558

HenriRabalais opened this issue May 13, 2019 · 14 comments
Assignees
Labels
Area: UI PR or issue related to the user interface State: Stale PR that has had no recent activity, needs to be triaged for review or closure to proceed

Comments

@HenriRabalais
Copy link
Collaborator

HenriRabalais commented May 13, 2019

Item #11 of the Test Plan:
Ensure that clicking on any row in the 'Archive Location' column triggers a download of the corresponding archived DICOM study. Make sure that the copy of the file downloaded to your system is prepended with the Patient Name field. [Manual Testing]

When a file does not exist and the user attempts to download it, they are led to a blank page and are not told that the file could not be found. Ideally, files that do not exist should not be hyperlinked, or the user should be warned after click on the link that the file could not be found.

@johnsaigle johnsaigle added the Area: UI PR or issue related to the user interface label May 13, 2019
@nicolasbrossard
Copy link
Contributor

When I tested this on the test VM for a file that does not exist, I get an HTTP 404 error page (not a blank page). I agree that if the file does not exist it should not be clickable but there could technically be other reasons why the file cannot be downloaded (permission issues, file size limit, possible others...) So instead of checking all things that could go wrong, I'd be in favour of displaying the 404 page. I am open to discussions though. @HenriRabalais Let me know what you think

@HenriRabalais
Copy link
Collaborator Author

@nicolasbrossard
I completely agree! If the 404 page displays properly, and the user is told that the file cannot be found, then I think the bug can be resolved!

For some reason I wasn't getting that error message displayed.

@maltheism
Copy link
Member

@HenriRabalais @nicolasbrossard I'm not getting the 404 page displayed on my workstation either. I'm just seeing a white page after clicking on one of the files.

@nicolasbrossard
Copy link
Contributor

@maltheism what do you get when you click on archive 2009/DCM_2009-06-09_ImagingUpload-14-14-qM69wJ.tar?

@maltheism
Copy link
Member

@nicolasbrossard On safari & firefox I'm getting a white page. On Chrome: The page can't be found with an no webpage was found for the webaddress that shows http://localhost/mri/jiv/get_file.php?file=2009/DCM_2009-06-09_ImagingUpload-14-14-qM69wJ.tar. and then it say's Search Google for localhost mri jiv get file.

@ycAbout
Copy link
Contributor

ycAbout commented May 28, 2019

This problem still exist as of Test round 2.

TestPlan Item 11. Ensure that clicking on any row in the 'Archive Location' column triggers a download of the corresponding archived DICOM study. Make sure that the copy of the file downloaded to your system is prepended with the Patient Name field. [Manual Testing]

Problem:
Click on record MTL022_300022_V1 lead to error:
This test.loris.ca page can’t be found No web page was found for the web address: https://test.loris.ca/mri/jiv/get_file.php?file=2009/DCM_2009-06-09_ImagingUpload-14-14-qM69wJ.tar&patientName=MTL022_300022_V1 HTTP ERROR 404

@johnsaigle
Copy link
Contributor

This seems like a Test VM issue. Now that Raisinbread contains MRI files to be downloaded the test VM seems to download these files without issue.

This issue could still occur if a file is deleted from the back-end without the DB table being updated. In this case a decorated 404 page should be displayed.

@johnsaigle
Copy link
Contributor

I can't replicate test this on my VM.

The files are stored on a read-only filesystem and I don't believe my user account has permission to change this.

@cmadjar
Copy link
Collaborator

cmadjar commented Nov 27, 2019

@johnsaigle I guess if you change the path in the config module to a different path than /data-raisinbread/ for the image path, that should replicate the tarchive files not being found. A bit hacky but as long as it works.

@johnsaigle
Copy link
Contributor

True, I'll try that

@stale
Copy link

stale bot commented Jan 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the State: Stale PR that has had no recent activity, needs to be triaged for review or closure to proceed label Jan 26, 2020
@stale
Copy link

stale bot commented Feb 18, 2020

The Stale label is being removed automatically because some activity has occurred or because the developers have decided that this pull request is important and should not continue to be overlooked.

@stale stale bot removed the State: Stale PR that has had no recent activity, needs to be triaged for review or closure to proceed label Feb 18, 2020
@stale
Copy link

stale bot commented Apr 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the State: Stale PR that has had no recent activity, needs to be triaged for review or closure to proceed label Apr 18, 2020
@johnsaigle
Copy link
Contributor

The crashing should be resolved by #6076 but I have not actually done the verification I said I would earlier... I hope to get to it after the release.

@regisoc regisoc mentioned this issue Apr 10, 2023
14 tasks
@driusan driusan closed this as completed Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: UI PR or issue related to the user interface State: Stale PR that has had no recent activity, needs to be triaged for review or closure to proceed
Projects
None yet
Development

No branches or pull requests

9 participants