-
Notifications
You must be signed in to change notification settings - Fork 110
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
ENH: Record a dataset's ID in a superdataset on add/save
(fixes gh-3303)
#3304
Conversation
d254ad3
to
ac85a35
Compare
Should be ok... but the code which starts relying on it (probably should later add check to install/clone) should assure to not crash if there is no ID recorded. |
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.
Makes sense.
The --add
in the git config
call made me pause, but I suppose it doesn't matter in practice.
Well, tests are going nuts in a few places. Apparently |
I think I should move this into |
…aladgh-3303) Otherwise we have incomplete identity information on all dataset components (i.e. we only have the state of a subdataset, but not its persistent ID). This is an issue during metadata extraction, where we would require subdatasets to be around in order to be able to give a full report. We already ensure that create(force=True) does not alter a dataset's ID, so getting out of sync would require manual fiddling with DataLad's internal config. Sure be safe...
Codecov Report
@@ Coverage Diff @@
## master #3304 +/- ##
==========================================
+ Coverage 91.03% 91.04% +<.01%
==========================================
Files 263 263
Lines 34221 34229 +8
==========================================
+ Hits 31154 31163 +9
+ Misses 3067 3066 -1
Continue to review full report at Codecov.
|
Finally! |
Otherwise we have incomplete identity information on all dataset components (i.e. we only have the state of a subdataset, but not its persistent ID). This is an issue during metadata extraction, where we would require subdatasets to be around in order to be able to give a full report.
We already ensure that create(force=True) does not alter a dataset's ID, so getting out of sync would require manual fiddling with DataLad's internal config. Sure be safe...