-
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
Support unsetting config via datalad -c :<name>
#6864
Conversation
As documented in datalad#5653 (comment) this API was lacking a method to unset configuration items, while all other API do support this feature. This changeset adds it. Closes datalad#6863
Instead of running a complete `wtf` for just getting the config listed, limit to this particular section. This cuts the runtime in half down to 3.7s for the entire file (rather than the previously annotated 11s for this one test.
Codecov Report
@@ Coverage Diff @@
## maint #6864 +/- ##
==========================================
+ Coverage 90.27% 91.23% +0.95%
==========================================
Files 354 354
Lines 46123 46127 +4
==========================================
+ Hits 41637 42083 +446
+ Misses 4486 4044 -442
Continue to review full report at Codecov.
|
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.
Looks LGTM but left some "stylistic" recommendations and filed related but not directly to this PR #6865
As suggested by @yarikoptic. This adds `(...|...)` to ways of describing the concept of alternative values in the CLI. We already use `...|...` and `{..., ...}`. But given the absence of style guidelines, this change should be ok. Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
I filed #6866 to capture one outcome of this PR. I now noticed that one particular travis run fails wrt the new test. I am not 100% certain what this test run's purpose is, but this needs to be investigated before things can go further. I will not have the resources to do this soonish (was hoping to have this be an evening side-quest). I will put the PR into draft mode for now. Fell free to close, once it is hanging here for too long. I have no real ETA They key issue is turning on debug logging: this passes:
this fails
|
Works now. I remembered where to look for the solution. |
note that in #6864 (comment) two invocations are the same -- I guess should've changed log level to debug in bad one. |
all green, approved, let's proceed |
Yes, 'debug' as log level was the trigger. Adjusted the comment. |
As documented in #5653 (comment) this API was lacking a method to unset configuration items, while
all other API do support this feature. This changeset adds it.
Closes #6863
This PR is targeting
maint
. IMHO this is not a new feature, but rather a missing piece in the implementation of an existing feature. It is strictly backward compatible.