Repository navigation
chore(deps): update fuse3 to 0.10.0 - #360
Merged
Merged
Conversation
The samsoir/fuse3 fork now follows upstream master at the 0.10.0 release, which carries the configurable max_background and congestion_threshold contributed from here. What the fork adds on top is three macOS fixes: reply resilience (upstream PR #137), comma-joined mount options, and reply drops logged at debug. Only the fuse3 entry of Cargo.lock changes. `cargo update -p fuse3` also moved five unrelated windows-sys pins, so the two lines were edited by hand and checked with `cargo metadata --locked`. XEarthLayer implements the raw Filesystem trait and no batch_forget, so the 0.10.0 API changes need no code change here. Also notes in the macFUSE smoke test that it must run in a local terminal: over SSH macOS refuses the first read through the mount with EPERM, which reads like a mount regression and is not one. Refs #155
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.
What
Moves the fuse3 pin from 0.9.0 (
8b3e390) to 0.10.0 (a7314f9c) onsamsoir/fuse3master.The fork was synced with upstream in samsoir/fuse3#3 and now equals upstream master (the 0.10.0 release plus Sherlock-Holo/fuse3#144) with three macOS fixes on top: reply resilience (Sherlock-Holo/fuse3#137), comma-joined mount options, and reply drops logged at debug. The configurable
max_backgroundandcongestion_thresholdare upstream as of 0.10.0.Cargo.lock: the fuse3 entry only.cargo update -p fuse3also moved five unrelatedwindows-syspins, so the two lines were edited by hand and checked withcargo metadata --locked.Filesystemtrait and nobatch_forget, so the 0.10.0 API changes do not reach it.xearthlayer/Cargo.tomlcomment,CLAUDE.mdandCHANGELOG.mddescribe the fork as it is now, including the rule that itsmasteris never rewritten because released lock files pin its commits.tests/macfuse_smoke.rs: a header note that the live smoke tests must run in a local terminal. Over SSH macOS refuses the first read through the mount withEPERM, because the session belongs tosshd-keygen-wrapper, which has no access to network volumes.This lands on its own, ahead of the FSKit work in #357, so a regression from 0.10.0 can be told apart from one in the new transport.
Refs #155
Verification
make pre-commiton Linux: passed (fmt, clippy, all tests, release script tests).make verify-macoson a Mac Studio in a local terminal, macFUSE kernel extension 5.3.3: passed, including both live macFUSE smoke tests. This is the first run of the merged reply write path against a real mount.develop/0.5.1on that Mac, so the baseline was green before the bump.