From d48049bdd892288b0e8b4e6d6ff65716f1ed4a49 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 10 Aug 2020 16:03:46 -0400 Subject: [PATCH] comment --- ..._a1bce716987b0d8d00a4a9aa07e9ac65._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/Recent_hang_with_rsync_remote_with_older_systems___40__Xenial__44___Jessie__41__/comment_13_a1bce716987b0d8d00a4a9aa07e9ac65._comment diff --git a/doc/bugs/Recent_hang_with_rsync_remote_with_older_systems___40__Xenial__44___Jessie__41__/comment_13_a1bce716987b0d8d00a4a9aa07e9ac65._comment b/doc/bugs/Recent_hang_with_rsync_remote_with_older_systems___40__Xenial__44___Jessie__41__/comment_13_a1bce716987b0d8d00a4a9aa07e9ac65._comment new file mode 100644 index 0000000000..69548cba1e --- /dev/null +++ b/doc/bugs/Recent_hang_with_rsync_remote_with_older_systems___40__Xenial__44___Jessie__41__/comment_13_a1bce716987b0d8d00a4a9aa07e9ac65._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 13""" + date="2020-08-10T19:54:26Z" + content=""" +Well, I ran the reproducer script, substituting a git-annex tarball with +the fix (and adding an output of the exit code and dropping the --debug), +and the end was: + + get f0 (from r...) + SHA256E-s2--9a271f2a916b0b6ee6cecb2426f0b3206ef074578be55d9bc94f6f3fe3ab86aa2 + 100% 1.95kB/s 0:00:00 (xfr#1, to-chk=0/1) + (checksum...) ok + (recording state in git...) + 0 + +So, I guess this patch is ok, at least with the git-annex I've built. +(Using haskell from debian unstable.) It seems possible that some older +ghc, async, etc might have handled that AsyncCancelled differently and +resulted in the behavior you're seeing. + +Also tried with https://downloads.kitenet.net/git-annex/autobuild/i386-ancient/git-annex-standalone-i386-ancient.tar.gz +and it's ok too. +"""]] -- 2.30.2