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

update

Browse source
This commit is contained in:
Joey Hess 2021-10-20 13:48:37 -04:00
parent 2801528eb2
commit dfe5a98286
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 6 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_8_cb7ce88ae3d77b9ba0a4e33c2321a3e1._comment
View file

@ -1,24 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
subject="""comment 8"""
date="2021-10-20T17:04:09Z"
content="""
@asakurareiko oh that's encouraging that I seem to be on the right track.
Adjusted branches still have the same error?
Although I was not aware that this test case in your comment #8 failed
before?
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.
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.
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.
"""]]