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: tox-dev/filelock
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3.25.1
Choose a base ref
...
head repository: tox-dev/filelock
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.25.2
Choose a head ref
  • 2 commits
  • 3 files changed
  • 2 contributors

Commits on Mar 11, 2026

  1. 🐛 fix(unix): suppress EIO on close in Docker bind mounts (#513) 

    Since 3.20.4, releasing a `UnixFileLock` inside Docker on macOS with
bind-mounted filesystems raises `OSError: [Errno 5] Input/output error`
on `os.close(fd)`. 🐛 The root cause is the `unlink → flock unlock →
close` sequence in `_release()`: some FUSE-backed bind-mount drivers
return `EIO` when closing an fd whose directory entry was already
removed.

The `unlink` must stay before `unlock` to prevent a race where a
concurrent acquirer locks the old inode while a new file is created, so
reordering is not an option. Instead, `os.close(fd)` is now wrapped in
`suppress(OSError)`, matching the existing treatment of `unlink`. At
that point the lock is already released and POSIX guarantees the fd is
invalidated regardless of the `close` return value, so suppressing the
error is safe.

Fixes #512
    @gaborbernat
    gaborbernat authored Mar 11, 2026
    Configuration menu
    Copy the full SHA
    42b740a View commit details
    Browse the repository at this point in the history

  2. Release 3.25.2

    @gaborbernat
    gaborbernat committed Mar 11, 2026
    Configuration menu
    Copy the full SHA
    5b9872c View commit details
    Browse the repository at this point in the history
Loading