From 95032bfae7f3f9b57ecddc0a7acc2e962bb8396e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 20 Oct 2021 13:12:16 -0400 Subject: [PATCH] update per other comment --- ...mment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment} | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) rename doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/{comment_7_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment => comment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment} (52%) diff --git a/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment b/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment similarity index 52% rename from doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment rename to doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment index c63d1c2666..88a1727d0e 100644 --- a/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment +++ b/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment @@ -3,13 +3,22 @@ subject="""comment 7""" date="2021-10-20T17:04:09Z" content=""" +@asakurareiko oh excellent news! + +Before I saw that it's apparently fixed, I noticed that git-annex opened a second connection to the database for writes, in addition to the connection it used for reads. That seems likely to be -involved in whatever locking problem there is on WSL. +involved in whatever locking problem there is on WSL. While maybe I already +fixed the main one, the fact that fix works makes me even more suspicious +about situations where there are multiple database connections. Commit [[!commit d0ef8303cf8c4f40a1d17bd134af961fd9917ca4]] eliminates that second connection. But there's some chance I'll have to revert it. If you test, please include `git-annex version` output so I can make sure you have a version with that change. + +I also wonder if this means that running 2 git-annex commands +simulantaneously will sometimes result in the same sqlite problem, despite +these fixes. """]]