Null merge 9.7 into trunk (catch-up after #1791) - #1795
Merged
satya-bodapati merged 6 commits intoSep 3, 2026
Conversation
…2-8.4 PXB-3502 [8.4]: Process largest files first in all parallel phases
…3-8.4 PXB-3863 [8.4]: Fix xbcloud with Azure Hierarchical Namespace (HNS) storage
…3-8.4 PXB-2553 [8.4]: Fix stacktrace assertion in bug766305 test
Null merge 8.4 into 9.7
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
2 participants
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.
Second sync round: #1792 was cut from 9.7 before #1791 landed, so trunk is still missing the 8.4->9.7 null-merge ancestry. This catches trunk up to current 9.7. Verified zero content delta. After this lands, #1794 lists only the PXB-3862 commits.