Skip to content

fix(p2p-12): prefer deepest matching mount lookup (#671)#751

Open
jlon wants to merge 21 commits intoCurvineIO:mainfrom
jlon:p2p-12-unified-boundary-hardening
Open

fix(p2p-12): prefer deepest matching mount lookup (#671)#751
jlon wants to merge 21 commits intoCurvineIO:mainfrom
jlon:p2p-12-unified-boundary-hardening

Conversation

@jlon
Copy link
Copy Markdown
Contributor

@jlon jlon commented Mar 26, 2026

Summary

  • Fix mounted-path lookup to prefer the deepest matching mount.
  • Keep this as a detached side PR; later P2P slices do not depend on broader unified refactors.

Design

  • Limit scope to the independently mergeable boundary bug in mount selection.
  • Exclude write-type, consistency, and route changes that depend on later mount-model evolution.

Implementation

  • Update mount cache lookup to choose the deepest valid match for overlapping mounts.
  • Leave cache sync and unified filesystem route changes out of this PR.

Verification

  • Verify overlapping mounts resolve to the deepest matching mount.
  • Verify non-overlapping mount selection remains unchanged.

@jlon
Copy link
Copy Markdown
Contributor Author

jlon commented Mar 26, 2026

Part 12/17 of the split P2P series that supersedes #671.

This PR targets , so the visible diff is cumulative. Review the slice described in this PR body instead of treating the whole diff as new.

Detached side PR. Review after #752; later slices do not depend on this one.

@jlon
Copy link
Copy Markdown
Contributor Author

jlon commented Mar 26, 2026

Review note: this is part 12/17 of the split P2P series that supersedes #671.

This PR targets main, so the visible diff is cumulative. Please review the slice described in this PR body.

Detached side PR. Review after #752; later slices do not depend on this one.

@jlon jlon force-pushed the p2p-12-unified-boundary-hardening branch from d47005c to 1ed58e1 Compare March 26, 2026 10:26
@jlon jlon force-pushed the p2p-12-unified-boundary-hardening branch from 1ed58e1 to d1ae906 Compare March 27, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant