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

comment

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

23
doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_9_b0700fdf101f6cc883857b293cd35267._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 9"""
date="2021-10-20T17:15:27Z"
content="""
The crash shows that runSqliteRobustly called `rethrow "while opening
database connection"`, and I think it was in the "| otherwise" branch
because the error is not Sqlite.ErrorIO.
So, it may also possibly help to handle Sqlite.ErrorProtocol,
which seems like what the actual error is from the message.
Handling it the same as Sqlite.ErrorBusy would make opening the db
be retried until whatever else had it open closes it, or finishes
the operation that is causing the problem. On the other hand,
that might make git-annex hang until another git-annex process exits,
which would not be helpful. So perhaps it would be better to handle it
like Sqlite.ErrorIO is handled, waiting for up to 1/10th of a second.
But perhaps that would not be enough of a wait.
Anyway, this is a note to myself: If concurrent git-annex processes on Windows
still have this problem, try catching Sqlite.ErrorProtocol and experiment
with different ways to handle it.
"""]]