From c6d1c7d2098c01cf4b419b4b48ef1b3e3ea951d4 Mon Sep 17 00:00:00 2001 From: jwodder Date: Thu, 21 Oct 2021 01:35:48 +0000 Subject: [PATCH] --- doc/bugs/metadata_cmd._vs._--json-error-messages.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 doc/bugs/metadata_cmd._vs._--json-error-messages.mdwn diff --git a/doc/bugs/metadata_cmd._vs._--json-error-messages.mdwn b/doc/bugs/metadata_cmd._vs._--json-error-messages.mdwn new file mode 100644 index 0000000000..9f5524636c --- /dev/null +++ b/doc/bugs/metadata_cmd._vs._--json-error-messages.mdwn @@ -0,0 +1,6 @@ +(Sorry about the title; I was trying to work within the character limit.) + +When invoking `git-annex metadata --batch --json --json-error-messages`, if an error occurs in response to some input — say, because the name of a nonexistent file was supplied (or, in my case, because the name of a file downloaded milliseconds ago in a parallel addurl process was supplied) — then `git-annex metadata` will output "git-annex: not an annexed file: {filepath}" to standard error and immediately exit. Not only is this in contrast to what it seems `--json-error-messages` should do, but the "exiting immediately" bit is in contrast to my understanding of how batch mode is supposed to work. Surely this should be fixed? + +[[!meta author=jwodder]] +[[!tag projects/dandi]] -- 2.30.2