-
Notifications
You must be signed in to change notification settings - Fork 17
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
Container ID ProjectName must start with project- or container- #254
Comments
This is a regression. Thanks for reporting. |
This should be fixed in the upcoming release. |
* Removing reliance on dxjava file download * Adding dxda to the platform asset * Creating manifests for dxda. Requires getting part information for files. * Adding a file to store the manifest, and using bz2 to compress it in the shell * Improving the situation with files having projects * Fixing bug #254 * Running dx-download-agent from the root directory
Fixed in release 1.06. Please take a look, and reopen if this doesn't work. |
Hi @orodeh , I'm still getting the same error in 1.06. I can't reopen this issue though. |
Interesting. Can you check release 1.07? I wonder if it is the same bug. If not, it will have to wait for next week. |
That didn't help, I'm still getting:
|
Although now it seems to be getting past the step that resulted in error before:
Worth noting is the fact that we use |
@pkaleta Could you include all the details so I can reproduce this problem in my environment? I also need the exact stack trace. I have several tests that use file paths as above, and they all work. For example: I am not sure where the problem is occurring. |
I believe commit (01cbfe2) fixes this bug on master branch. |
@pkaleta Can you please try out release 1.08 https://github.com/dnanexus/dxWDL/releases/tag/1.08, I believe it fixes this issue, and the download-agent problem you ran into. |
@orodeh
In dxWDL 1.05, I've started getting the following exception during compile:
In my
extras.json
I have this, which worked up until 1.04:Is it no longer valid to use the
dx://ProjectName:/file/path.vcf.gz
format and I have to usedx://proj-xxxx:file-yyyy::ProjectName/file/path.vcf.gz
instead? Or is this a regression?The text was updated successfully, but these errors were encountered: