Fix: ZipperHead fixes - #133
Merged
luketpeterson merged 4 commits intoSep 25, 2026
Merged
luketpeterson merged 4 commits into
luketpeterson merged 4 commits into
Conversation
With an empty path and the head's root inside a node, the walk popped a byte of the head's own path and never put it back. The next request then read past its key buffer (UB in release) or panicked.
as_static_path_zipper asserted the zipper held no borrowed origin path, but write_zipper_at_path always does. Once buffers are prepared the path lives in prefix_buf, so drop the borrowed slice instead.
make_cell_node called make_mut on the empty sentinel, which panics. Replace the sentinel with a new CellByteNode instead.
Collaborator
|
I was initially confused because this PR originally held 3 separate ZH fixes. But the PRs that came before it contained 2 of them. So, on top of the master branch with the others merged, this PR covers the case where the an empty node sentinel needs be upgraded to a CellByteNode to support a ZipperHead. Good fix. Merging. |
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.
Fix ZipperHead exclusive path at the head's own root
With an empty path and the head's root inside a node, the walk popped a
byte of the head's own path and never put it back. The next request then
read past its key buffer (UB in release) or panicked.
Fix zipper_head on a write zipper with a borrowed path
as_static_path_zipper asserted the zipper held no borrowed origin path,
but write_zipper_at_path always does. Once buffers are prepared the path
lives in prefix_buf, so drop the borrowed slice instead.
Fix ZipperHead exclusive paths over an empty node
make_cell_node called make_mut on the empty sentinel, which panics.
Replace the sentinel with a new CellByteNode instead.