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
BF: RIA cloning #5255
BF: RIA cloning #5255
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.
Thanks. Looks good to me aside from the import issue I noted.
Even if we expect 0.14 out before another maintenance release, I'm guessing you intended to choose maint rather than master as the base for this PR?
@@ -918,9 +933,6 @@ def postclonecfg_annexdataset(ds, reckless, description=None): | |||
yield from configure_origins(ds, ds) | |||
|
|||
|
|||
_handle_possible_annex_dataset = postclonecfg_annexdataset |
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.
There's also an import in the deprecated datalad.distribution.clone
.
Codecov Report
@@ Coverage Diff @@
## maint #5255 +/- ##
=======================================
Coverage 90.43% 90.44%
=======================================
Files 294 294
Lines 40936 40962 +26
=======================================
+ Hits 37021 37047 +26
Misses 3915 3915
Continue to review full report at Codecov.
|
Re Re import: Indeed. How did git-grep not find it? Anyway, will remove, too. Thx! |
crippledFS failures look unrelated. Do they seem famililar, @datalad/developers ? |
At least the |
Thanks! I agree that it should go into |
The bare repos in a RIA store are intended to not have a local annex they know of, although there is an annex/ dir for access via ORA special remote as well as for enabling workflows using ephemeral clones symlinking into that location. However, if we clone from local FS, annex-init on the clone may also initialize origin, posing a danger for messing up availability info. Prevent that by setting annex-ignore before we initialize the clone (we used to do that afterwards anyway). (Closes datalad#5186)
Thx! |
I was too quick and did not acknowledge I have cleanup up |
Fixes #5186
Sits on top of PR #5254 due to #5253, which is not the same but a somewhat related issue.
Despite @mih's hesitance, I'd like to support RIA stores without any ORA remote. Since an ID based structure for standard, bare annex repos is perfectly valid and requires all the same stuff (URL resolution for example). In such a case this fix would not fix but sabotage the intended behavior. With that in mind, this one-liner is a function, that can be enhanced to first query the store for a to be introduced dataset level layout, that would disable the
annex-ignore
setting.