root cause analysis
This commit is contained in:
parent
da2c02162c
commit
61ed0b3f03
2 changed files with 16 additions and 4 deletions
doc/bugs/annex_merge__breaks_git_repository__33__
|
@ -6,8 +6,4 @@
|
|||
Spotchecked a few other OpenNeuro datasets in the same numeric range and
|
||||
they seem ok, so this may have been a 1-off problem. It would be good to
|
||||
check all 1.1k datasets.
|
||||
|
||||
One possible way this might happen: git-annex is performing a transition,
|
||||
and gets interrupted after making the commit starting the new git-annex
|
||||
branch, but before it can graft in the export trees.
|
||||
"""]]
|
||||
|
|
|
@ -0,0 +1,16 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 5"""
|
||||
date="2024-06-03T17:28:02Z"
|
||||
content="""
|
||||
performTransitionsLocked, when `neednewlocalbranch = True`,
|
||||
first writes the new git-annex branch, and then calls
|
||||
regraftexports which adds a second commit onto it.
|
||||
|
||||
In the window before regraftexports finishes, interrupting git-annex will
|
||||
leave the repository in this state.
|
||||
|
||||
There may be some other way this could happen, but that seems like a likely
|
||||
cause. It needs to avoid updating the git-annex branch ref until it's
|
||||
grafted the exports into it.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue