Bump github.com/fsnotify/fsnotify from 1.6.0 to 1.8.0

[dependabot]

Bumps github.com/fsnotify/fsnotify from 1.6.0 to 1.8.0.

Release notes

Sourced from github.com/fsnotify/fsnotify's releases.

v1.8.0

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

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.

... (truncated)

Changelog

Sourced from github.com/fsnotify/fsnotify's changelog.

1.8.0 2023-10-31

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)

#590: fsnotify/fsnotify#590 #610: fsnotify/fsnotify#610 #617: fsnotify/fsnotify#617 #619: fsnotify/fsnotify#619 #620: fsnotify/fsnotify#620 #621: fsnotify/fsnotify#621 #625: fsnotify/fsnotify#625 #650: fsnotify/fsnotify#650

1.7.0 - 2023-10-22

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

... (truncated)

Commits

• a9bc2e0 Prepare 1.8.0 release
• 2d133b8 inotify: fix panic on Remove()
• 1626962 Update CI
• c1467c0 test/kqueue: watch symlinks
• 800ed83 kqueue: don't change internal state when Add() returns error (#638)
• ad74244 remove extra "to" from doc comment (#634)
• bec8903 Split out Watcher and backends (#632)
• a618f07 inotify: add recursive watcher (#472)
• 17d9053 Print diffs for test failures
• 53b06a8 inotify: implement WithNoFollow() (#631)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign skmatti for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment