-
Notifications
You must be signed in to change notification settings - Fork 1
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
refactor: Rewrite data cp implementation #506
Conversation
e277a88
to
084912b
Compare
c22a483
to
7fe4d3c
Compare
097e090
to
8f55e7a
Compare
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.
Great job, thank you a lot for refactoring the spaghetti code we have written :)
All looks good to me, only some suggestions came to my mind, apply them or not - up to you.
…extras into refactor/data_cp
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.
The code LGTM, great job, man!
Please, let's get the tests working before merging.
e2e tests are addressed in #515 |
Test finally passed, but from now on when running e2e tests we need to check test logs, as some tests might Resolving #512 might help alleviate this problem a little. |
This PR addresses many issues with previous code for
neuro-extras data cp
command (#500,#301). Main idea of the proposed changes is to modularize key processes, related to data copy and add some useful abstractions to simplify further addition of supported sources/destinations (like neu.ro platform buckets or Google Drive #235).Readiness checklist
source
/destination
combinations are fully supportedstorage:
anddisk:
only)New(will be in a separate PR)ExistPassing