-
Notifications
You must be signed in to change notification settings - Fork 4
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
User studies: When an install fails, still seeing a status of "installing" #38
Comments
Error from Logs https://ws.qa.apidb.org/job/irods-handler-ClinEpiDB/76/label=irods-north/console:
Event 165704282300012765 seems to be marked as failed in database according to @steve-fischer-200 |
Just took a look at the client code. It seems like for uninstalled UDs, we always display “installing” if less than four hours have passed since the UD’s creation. If more than four hours have passed, we display an “error.” |
It seems like the existing UD response doesn’t provide an “error” field for UDs which failed to install. Not sure why. |
Paused while UI/Infra assesses a rehaul of the User Datasets system, which would likely obviate the need to fix this big |
@jtlong3rd are we ready to take another look at this ticket? please close it if the rehaul fixed the issue. thanks! |
I spoke with Jamie about this issue. The backend currently uses IRODs, which is, in part, responsible for the issue. The backend will need to migrate away from IRODs to address this issue. I don't know when that might happen, but definitely not any time soon. |
ok, i am moving this out of b60. thanks |
this will be reviewed in the context of the new VDI |
See slack thread: https://epvb.slack.com/archives/CBEA7PQDQ/p1657045518138049
Basically, I tried to upload the PRISM_cohort_Participants.txt file as a user study. I received no error message on import or install, but even though the logs showed the install failed within a few min, 40 min later I still saw the status as "installing". This ticket is specifically to address the bug where an install failed but was not reported as a failure.
The text was updated successfully, but these errors were encountered: