From d99380be85fd5da77ae142d39ccb20e36444b5ba Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 22 Sep 2025 11:15:32 -0400 Subject: [PATCH] comment --- ...mment_1_bce639fd90df8d8a3160a3425e4cb927._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Unlock_filter_seems_to_deadlock_for_huge_worktree/comment_1_bce639fd90df8d8a3160a3425e4cb927._comment diff --git a/doc/bugs/Unlock_filter_seems_to_deadlock_for_huge_worktree/comment_1_bce639fd90df8d8a3160a3425e4cb927._comment b/doc/bugs/Unlock_filter_seems_to_deadlock_for_huge_worktree/comment_1_bce639fd90df8d8a3160a3425e4cb927._comment new file mode 100644 index 0000000000..a51416c12e --- /dev/null +++ b/doc/bugs/Unlock_filter_seems_to_deadlock_for_huge_worktree/comment_1_bce639fd90df8d8a3160a3425e4cb927._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2025-09-22T15:14:03Z" + content=""" +10240 is a very specific number, and is the *same* number that annex.queuesize +default to. + +So, that seems very likely to be the root of the problem, and at least +configuring annex.queuesize to something larger may work around the +problem. +"""]] -- 2.30.2