Repository navigation
Detect failed reads when a tree is missing from a DF - #15978
Merged
Merged
Conversation
Member
|
Thank you for your contribution. The change itself is fine. I have some refactoring I am currently doing which might conflict with this. If you do not mind, can you wait a bit more for this to be merged? |
Contributor
Author
|
I'm currently on holiday until the 5th, so no problem. |
Contributor
Author
|
Should be ready to merge again now |
Member
|
thanks. please rebase and squash your commits when doing merge conflicts resolution. |
This file contains hidden or 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
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.
Detect ROOT key-read failures during AOD table lookup, so a failed read is not treated as a missing tree