Fix manifest load-all chunk selection#27
Merged
zipproth merged 1 commit intoacrion:developfrom Apr 10, 2026
Merged
Conversation
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.
This follow-up fixes the manifest-mode load-all path after PR #25.\n\nProblem\n- When no explicit chunk selectors are provided, the corresponding selection pointer is null, but the inner per-chunk loop still checked the selection set and skipped every chunk.\n- That meant could load no payload chunks even though omitted selectors are documented to mean load all.\n\nFix\n- Apply the per-chunk selection filter only when the corresponding selection pointer is non-null.\n- The change is applied symmetrically for left, right, nameOfNode, and nodeOfName.\n\nValidation\n- Rebased onto current .\n- Local rebuild passed.\n\nThis is the issue Stefan flagged in the PR #24 thread and again after PR #25.