Skip to content
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

local to subdatasets paths in action status report are misleading #3442

Closed
yarikoptic opened this issue May 20, 2019 · 1 comment
Closed

Comments

@yarikoptic
Copy link
Member

if before (0.11.x) it was suboptimal due to full paths:

(git-annex)hopa:/tmp/testds-remove[master]git-annex
$> echo 123 >> subds/subds12/subds/ingit 
(dev) 1 14595 [2].....................................:Mon 20 May 2019 06:38:30 PM EDT:.
(git-annex)hopa:/tmp/testds-remove[master]git-annex
$> datalad save -r -d . subds/subds12/subds/ingit
save(ok): /tmp/testds-remove/subds/subds12/subds (dataset)
save(ok): /tmp/testds-remove/subds/subds12 (dataset)
save(ok): /tmp/testds-remove/subds (dataset)
save(ok): /tmp/testds-remove (dataset)
action summary:
  save (ok: 4)

Now (0.12.0rc4.dev5) it is easier on eyes but without consideration of the "context" from which the command was called, reported paths within subdatasets could be confusing, wrong, or misleading:

(git-annex)hopa:/tmp/testds-remove[master]git-annex
$> echo 123 >> subds/subds12/subds/ingit
(dev) 1 14599 [2].....................................:Mon 20 May 2019 06:39:20 PM EDT:.
(git-annex)hopa:/tmp/testds-remove[master]git-annex
$> datalad save -r -d . subds/subds12/subds/ingit
add(ok): ingit (file)
save(ok): subds/subds12/subds (dataset)
add(ok): subds (file)
save(ok): subds/subds12 (dataset)
add(ok): subds12 (file)
save(ok): subds (dataset)
add(ok): subds (file)
save(ok): . (dataset)
action summary:
  add (ok: 4)
  save (ok: 4)

not to mention that I am not sure what "add(ok): subds (file)" means since I do not have subds file in this example.

@mih
Copy link
Member

mih commented Nov 7, 2021

Thank you for reporting this issue!

However, at this point I am closing it at a time of ~600 open issues, in an attempt to regain control over the issue tracker. This particular issue was posted more than 6 months ago, has not received a single response, and does not describe an immediate software defect. Closing this issue does not imply that it is not relevant. If any reader objects the closing of this issue, please feel more than free to reopen it with an update on how it is relevant for the current state of the project, and which concrete actions to address it are ongoing or planned.

@mih mih closed this as completed Nov 7, 2021
Tackle user experience issues automation moved this from Needs triage to Closed Nov 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants