fsspec / fsspec/filesystem_spec

fsspec.fuse -f is inverted and hangs when specified

Open
#1,586 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.4k
Forks
490
Avg merge
2d 3h
Merged PRs (30d)
38

Description

echo bar > foo
tar -cf foo{.tar,}
python3 -m fsspec.fuse --version  # 2024.3.1
python3 -m fsspec.fuse --help
#  -f, --foreground      Running in foreground or not (Default: False)
python3 -m fsspec.fuse local foo.tar mounted  # Runs in the foreground contrary to the help message
python3 -m fsspec.fuse -f local foo.tar mounted # Finishes / moves itself into background

As the comments in the above reproducer state:

  • Without -f, the called python process stays in the foreground even though the default value to -f is supposed to be False.
  • Note that the mount point cannot be read because of #1568.
  • With -f specified, the program moves itself into the background. So, the exact opposite what it should do.
  • With -f, the mount point hangs every process trying to access it. E.g., try running ls in the folder the mount point is in, and it will hang. fusermount -u also does not work. The started python process has to be searched with pgrep or ps and killed manually: kill $( pgrep -f fsspec )

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the fsspec.fuse entry point and run the reproducer commands from the issue, comparing behavior with and without -f. Done means the foreground option matches its help text and the mounted path can be accessed and unmounted without hanging processes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.