From: Joey Hess <joeyh@joeyh.name>
Date: Tue, 13 May 2025 15:14:28 +0000 (-0400)
Subject: response
X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~7^2~171
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=e166a0632341915810cad41954b0d7e6194825fa;p=git-annex.git

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
index 0000000000..e335e1bda2
--- /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`
+"""]]