chore(deps): update module github.com/fsnotify/fsnotify to v1.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/fsnotify/fsnotify	v1.5.4 -> v1.8.0

---

Release Notes

fsnotify/fsnotify (github.com/fsnotify/fsnotify)

v1.8.0

Compare Source

Additions

• all: add FSNOTIFY_DEBUG to print debug logs to stderr (#​619)

Changes and fixes

• windows: fix behaviour of WatchList() to be consistent with other platforms (#​610)

• kqueue: ignore events with Ident=0 (#​590)

• kqueue: set O_CLOEXEC to prevent passing file descriptors to children (#​617)

• kqueue: emit events as "/path/dir/file" instead of "path/link/file" when watching a symlink (#​625)

• inotify: don't send event for IN_DELETE_SELF when also watching the parent (#​620)

• inotify: fix panic when calling Remove() in a goroutine (#​650)

• fen: allow watching subdirectories of watched directories (#​621)

v1.7.0

Compare Source

This version of fsnotify needs Go 1.17.

Additions

• illumos: add FEN backend to support illumos and Solaris. (#​371)

• all: add NewBufferedWatcher() to use a buffered channel, which can be useful in cases where you can't control the kernel buffer and receive a large number of events in bursts. (#​550, #​572)

• all: add AddWith(), which is identical to Add() but allows passing options. (#​521)

• windows: allow setting the ReadDirectoryChangesW() buffer size with fsnotify.WithBufferSize(); the default of 64K is the highest value that works on all platforms and is enough for most purposes, but in some cases a highest buffer is needed. (#​521)

Changes and fixes

• inotify: remove watcher if a watched path is renamed (#​518)

  After a rename the reported name wasn't updated, or even an empty string. Inotify doesn't provide any good facilities to update it, so just remove the watcher. This is already how it worked on kqueue and FEN.

  On Windows this does work, and remains working.

• windows: don't listen for file attribute changes (#​520)

  File attribute changes are sent as FILE_ACTION_MODIFIED by the Windows API, with no way to see if they're a file write or attribute change, so would show up as a fsnotify.Write event. This is never useful, and could result in many spurious Write events.

• windows: return ErrEventOverflow if the buffer is full (#​525)

  Before it would merely return "short read", making it hard to detect this error.

• kqueue: make sure events for all files are delivered properly when removing a watched directory (#​526)

  Previously they would get sent with "" (empty string) or "." as the path name.

• kqueue: don't emit spurious Create events for symbolic links (#​524)

  The link would get resolved but kqueue would "forget" it already saw the link itself, resulting on a Create for every Write event for the directory.

• all: return ErrClosed on Add() when the watcher is closed (#​516)

• other: add Watcher.Errors and Watcher.Events to the no-op Watcher in backend_other.go, making it easier to use on unsupported platforms such as WASM, AIX, etc. (#​528)

• other: use the backend_other.go no-op if the appengine build tag is set; Google AppEngine forbids usage of the unsafe package so the inotify backend won't compile there.

v1.6.0

Compare Source

This version of fsnotify needs Go 1.16 (this was already the case since 1.5.1, but not documented). It also increases the minimum Linux version to 2.6.32.

Additions

• all: add Event.Has() and Op.Has() (#​477)

  This makes checking events a lot easier; for example:

    if event.Op&Write == Write && !(event.Op&Remove == Remove) {
    }
  

  Becomes:

    if event.Has(Write) && !event.Has(Remove) {
    }
  

• all: add cmd/fsnotify (#​463)

  A command-line utility for testing and some examples.

Changes and fixes

• inotify: don't ignore events for files that don't exist (#​260, #​470)

  Previously the inotify watcher would call os.Lstat() to check if a file still exists before emitting events.

  This was inconsistent with other platforms and resulted in inconsistent event reporting (e.g. when a file is quickly removed and re-created), and generally a source of confusion. It was added in 2013 to fix a memory leak that no longer exists.

• all: return ErrNonExistentWatch when Remove() is called on a path that's
  not watched (#​460)

• inotify: replace epoll() with non-blocking inotify (#​434)

  Non-blocking inotify was not generally available at the time this library was written in 2014, but now it is. As a result, the minimum Linux version is bumped from 2.6.27 to 2.6.32. This hugely simplifies the code and is faster.

• kqueue: don't check for events every 100ms (#​480)

  The watcher would wake up every 100ms, even when there was nothing to do. Now it waits until there is something to do.

• macos: retry opening files on EINTR (#​475)

• kqueue: skip unreadable files (#​479)

  kqueue requires a file descriptor for every file in a directory; this would fail if a file was unreadable by the current user. Now these files are simply skipped.

• windows: fix renaming a watched directory if the parent is also watched (#​370)

• windows: increase buffer size from 4K to 64K (#​485)

• windows: close file handle on Remove() (#​288)

• kqueue: put pathname in the error if watching a file fails (#​471)

• inotify, windows: calling Close() more than once could race (#​465)

• kqueue: improve Close() performance (#​233)

• all: various documentation additions and clarifications.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.33%. Comparing base (4c2a4de) to head (bf69b5e).
Report is 17 commits behind head on 4.x.

Additional details and impacted files

@@           Coverage Diff           @@
##              4.x      #88   +/-   ##
=======================================
  Coverage   94.33%   94.33%           
=======================================
  Files          10       10           
  Lines         688      688           
=======================================
  Hits          649      649           
  Misses         36       36           
  Partials        3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.