Bug Fixes
-
retry the current commit when graph parents are corrupt
Both
Simpletraversal paths pop the current commit before decoding its
cached parents. If parent iteration fails, dropping the cache and recursively
requesting the next commit skips the popped commit and its entire ancestry.
With an out-of-range inline parent, a two-commitgixrevision walk could
therefore succeed with an empty result.Put the current commit back at the front of the topology queue or into the
date queue with its existing priority, then continue the loop after disabling
the cache. The object database retries that same commit without recursion;
any object lookup or decoding failure is still propagated.The regression corrupts a disposable graph, confirms that Git rejects it,
and checks that the existinggixfallback policy preserves both commits
across breadth-first traversal, both date orders, cutoff sorting, and
first-parent traversal.
Commit Statistics
- 5 commits contributed to the release over the course of 14 calendar days.
- 14 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Merge pull request #3066 from GitoxideLabs/check-commit-graph (7540f69)
- Retry the current commit when graph parents are corrupt (a7714e5)
- Merge pull request #3053 from GitoxideLabs/various-improvements (2d8dcc4)
- Release gix-error v0.5.1, gix-utils v0.5.1 (6d1b686)
- Merge pull request #3048 from GitoxideLabs/new-release (5fccccf)