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
Data access via DRS URIs frequently fails in Ammonite script #5069
Comments
Although I said "frequently fails" in the title of this issue, "always fails" would be more correct. This seemed to work for Commons in 2018, but I have not seen it work since I have been trying again in 2019. |
Hey @mikebaumann -- can you describe for the workflow/task you're running -- what are the # of input files? When you say it worked for the "commons" in 2018, how was this tested? Just for my understanding of the before/after. |
Hi @ruchim! Regarding our current test setup: Workflow: Single File: I just now ran this test configuration from scratch, starting with a new workspace, and it failed like all the others have: Error:
Log:
The name of this workspace is Regarding successful runs in Commons in 2018: |
Here is another Broad issue that is intrinsically related to this issue: |
Terra/Cromwell workflows using data that has been exported from the UChicago Gen3/Windmill system or the HCA Data Browser with DRS URI data references frequently (always?) fail in the Ammonite script that performs the DRS resolution/localization.
Failed workflows using DRS URI data references most often have error messages and logs as shown below. These examples are from the Terra workspace
firecloud-cgl/20190701 Test
in which a small number of files were exported from Windmill to Terra, and an md5sum workflow was exported from Dockstore. These same error messages and log entries have been seen in many other similar workspaces over the last couple/few months (no data before that).@abaumann has been recently and actively involved in the investigation of this problem, and has access to this workspace.
or
In some cases, additional information is logged, as in the following example where Ammonite dependency failed:
The text was updated successfully, but these errors were encountered: