From 20875bd5e8659a1ed30ce5f6bee87ce2082c8423 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 28 Feb 2022 13:26:43 -0400 Subject: [PATCH] open related todo --- ...ment_3_28060f4bb31730e3334cf3db56fc032b._comment | 3 ++- ...ng_when_nonexistant_or_non_git_files_passed.mdwn | 13 +++++++++++++ 2 files changed, 15 insertions(+), 1 deletion(-) create mode 100644 doc/todo/api_for_telling_when_nonexistant_or_non_git_files_passed.mdwn diff --git a/doc/bugs/no_longer_non-0_exit_for___34__find_..._nonexisting__34__/comment_3_28060f4bb31730e3334cf3db56fc032b._comment b/doc/bugs/no_longer_non-0_exit_for___34__find_..._nonexisting__34__/comment_3_28060f4bb31730e3334cf3db56fc032b._comment index b026f985a8..c824282c37 100644 --- a/doc/bugs/no_longer_non-0_exit_for___34__find_..._nonexisting__34__/comment_3_28060f4bb31730e3334cf3db56fc032b._comment +++ b/doc/bugs/no_longer_non-0_exit_for___34__find_..._nonexisting__34__/comment_3_28060f4bb31730e3334cf3db56fc032b._comment @@ -25,5 +25,6 @@ are never included in --json-error-messages. I think it might be a good idea to add an actual API for detecting when there is this kind of problem, so datalad does not have to parse error messages (which could easily change). But that would need to be a -separate discussion. +separate discussion. I've opened +[[todo/api_for_telling_when_nonexistant_or_non_git_files_passed]] for that. """]] diff --git a/doc/todo/api_for_telling_when_nonexistant_or_non_git_files_passed.mdwn b/doc/todo/api_for_telling_when_nonexistant_or_non_git_files_passed.mdwn new file mode 100644 index 0000000000..64fbe17c12 --- /dev/null +++ b/doc/todo/api_for_telling_when_nonexistant_or_non_git_files_passed.mdwn @@ -0,0 +1,13 @@ +As seen in datalad +is having to parse error messages to determine when nonexistant +filenames were passed to git-annex. It would be better if there was some +kind of API that it could use, since error messages can (and have) changed. + +What would this API look like? It seems it could not be a special +exit status of git-annex, because exit status 101 is already allocated +for indicating when things like --size-limit and --time-limit have caused +it to skip processing certian files. + +Perhaps something like `--json-error-unmatch` which would make it output +an additional line with a JSON record indicating that git ls-files +--error-unmatch had errored out. -- 2.30.2