Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: bazil/fuse
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: nestybox/fuse
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 5 commits
  • 5 files changed
  • 3 contributors

Commits on Jul 11, 2025

  1. Changed go-module to force utilization of our fork. 

    Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
    @ctalledo
    ctalledo committed Jul 11, 2025
    Configuration menu
    Copy the full SHA
    40f055f View commit details
    Browse the repository at this point in the history

  2. Readdir() extension to provide request-info to sysvisor-fs 

    [ci skip]

Fixes #234.
    @rodnymolina @ctalledo
    rodnymolina authored and ctalledo committed Jul 11, 2025
    Configuration menu
    Copy the full SHA
    7628c63 View commit details
    Browse the repository at this point in the history

  3. Minor extension to allow syscall.EACESS error to be generated back to… 

    … FUSE client

Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
    @ctalledo
    ctalledo committed Jul 11, 2025
    Configuration menu
    Copy the full SHA
    3c9b808 View commit details
    Browse the repository at this point in the history

  4. Improve logging of fuse request & response attributes. 

    Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
    @ctalledo
    ctalledo committed Jul 11, 2025
    Configuration menu
    Copy the full SHA
    473cbd7 View commit details
    Browse the repository at this point in the history

  5. Don't consider no-child-process sub-command error as such in some cases. 

    Due to a race-condition in Golang, it's possible that a cmd.Start() may result
in a "no child process" error even though the child process was created and in
fact succeeded. See kubernetes/kubernetes#103753 for
full context.

This change causes the code to ignore "no child process" errors if the
sub-command process succeeds.

Signed-off-by: Cesar Talledo <ctalledo@nestybox.com>
    @ctalledo
    ctalledo committed Jul 11, 2025
    Configuration menu
    Copy the full SHA
    5ce3194 View commit details
    Browse the repository at this point in the history
Loading