Repository navigation
Fix the FUSE CLI foreground option - #2352
Merged
martindurant merged 2 commits intoOct 21, 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
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.
Fixes #1586.
The FUSE CLI currently enables foreground mode without
-f, and disables it when-for--foregroundis supplied. Usestore_trueso the option matches its name and documented background default. The Pythonrun()API keeps its existing foreground default.Add three CLI-to-
run()regression cases and an API-default control. The existing local-mount fixture now passes-fexplicitly to keep its mount process in the foreground.Validation on Linux/Python 3.12.13:
pytest fsspec/tests/test_fuse.py -q: 8 passed, including the existing real FUSE mount/read/write/chmod/seek tests.pre-commit run --all-files: passed all applicable hooks, including pinned Ruff 0.14.3.Prepared with OpenAI Codex assistance for the implementation, tests and local verification.