mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update per other comment

Browse source
This commit is contained in:
Joey Hess 2021-10-20 13:12:16 -04:00
parent 77c0892e27
commit 95032bfae7
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 10 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment → doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment
View file

@ -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.
"""]]