-
Notifications
You must be signed in to change notification settings - Fork 28
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
WIP: initial support for ftp locations #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome thanks for adding this! This gives me a better idea of how we could support S3
Will this solve the issue #26 ? Can you add an ftp example? |
@fgypas That's the goal, but I'm having issues testing |
|
Hi. I would like to ask what is the status of this pull request. We would really need to have this working at the end of the month. Please let me know if there is anything I could do to help. |
Hi. I second the request by @fgypas. What is the status of remote storage support? How to run it? Could you provide an example with FTP? I tried hashsplitter, passing --remote-storage-url, but without success. |
Hello @fgypas and @aniewielska
The complete log: log-20180825.txt To run the CWL conformance tests, check out the CWL specification https://github.com/common-workflow-language/common-workflow-language/
You'll need the username and password set in
|
Thanks. I figured out .netrc part. Should Hashsplitter work, though, with remote FTP storage? If not, is there any other simple at least 2-step workflow (that will use intermediate remote storage, if configured, or local otherwise), that I can use to check, that I am using CWL-TES correctly? |
@aniewielska Hashsplitter and friends should work, but it doesn't due to a limitation in Here's how to run it
|
@aniewielska The hashsplitter tools and workflows work for me now:
|
@adamstruck The remaining errors are related to TES's poor support for empty directories. Shall I merge as in? |
I ran the test suite yesterday (without the most recent commits) and I got:
From the TESK perspective there were 7 tasks failing on inputs. In 5 cases TES received inputs with URLs referencing local file system. In 2 cases passed URL was malformed (file/ftp mix):
|
@mr-c the problem with empty directories IMO is that there isn't a way to represent it in an object store (without using placeholder files). From the TES perspective, the spec says nothing with regards to how to handle an input/output directory that is empty. So its possible Funnel and TESK have different behaviors around these cases. |
@mr-c prior to merging this I think it would be good to update the Travis build so that it runs the conformance suite against local files and FTP. We have some test code in Funnel (https://github.com/ohsu-comp-bio/funnel/tree/master/tests/ftp-test-server) for starting up a FTP server for testing that could be reused. |
What we were told when working on CWL in GCP (and thus object storage) was to add a dotfile to the directory so that it shows up in object storage as a "directory". IMO that's a terrible hack and frankly a bug in CWL (and soon to be replicated in WDL as well) that it doesn't neatly handle the impedance mismatch between POSIX & object storage, but it's not like I have any better idea on how to solve it so c'est la vie. Dotfiles it is :) With my GA4GH hat on I personally would oppose things which are not object storage friendly (it is the Cloud Workstream after all). |
For my reference, the failing test numbers are:
|
Current status: 121 tests passed, 4 failures, 8 unsupported features