fix tree parsing and error reporting #1098
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…le raw`. This is mainly useful to generate fixtures for the test-suite, and is assured to not add extra-bytes to the output either.
Fix the slow and the fast-path tree-parsers to be able to cope with a greater variety of trees.
…ects fails. When `verbose-object-parsing-errors` is enabled, it will now once again provide greater details as to where and why the parsing failed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #1096 .
Tasks
Postponed
gix-object/verbose-object-parsing-errorscan include more parsing state like withnom#1099CC @epage (just for your information, I might have questions when handling with restoring verbose parsing errors)