response

diff --git a/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_1_f4e0b61203f2f90be5f53003a6b08b52._comment b/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_1_f4e0b61203f2f90be5f53003a6b08b52._comment
new file mode 100644 (file)
index 0000000..e335e1b
--- /dev/null
+++ b/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_1_f4e0b61203f2f90be5f53003a6b08b52._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2025-05-13T15:06:43Z"
+ content="""
+I've seen this message before with `git-annex version | head -n 1`
+
+That particular one was made to ignore the error to write to stdout after
+it was closed, but any other write to stdout might fail similarly when
+going to a pipe that got closed.
+
+So can you please track down what git-annex command is being run? My
+suggestion is to use `strace -f`
+"""]]