fsnotify/fsnotify (github.com/fsnotify/fsnotify)
### [`v1.7.0`](https://togithub.com/fsnotify/fsnotify/releases/tag/v1.7.0)
[Compare Source](https://togithub.com/fsnotify/fsnotify/compare/v1.6.0...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.
- 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.
[#371]: https://togithub.com/fsnotify/fsnotify/pull/371
[#516]: https://togithub.com/fsnotify/fsnotify/pull/516
[#518]: https://togithub.com/fsnotify/fsnotify/pull/518
[#520]: https://togithub.com/fsnotify/fsnotify/pull/520
[#521]: https://togithub.com/fsnotify/fsnotify/pull/521
[#524]: https://togithub.com/fsnotify/fsnotify/pull/524
[#525]: https://togithub.com/fsnotify/fsnotify/pull/525
[#526]: https://togithub.com/fsnotify/fsnotify/pull/526
[#528]: https://togithub.com/fsnotify/fsnotify/pull/528
[#537]: https://togithub.com/fsnotify/fsnotify/pull/537
[#550]: https://togithub.com/fsnotify/fsnotify/pull/550
[#572]: https://togithub.com/fsnotify/fsnotify/pull/572
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 has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v1.6.0->v1.7.0Release Notes
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
### [`v1.7.0`](https://togithub.com/fsnotify/fsnotify/releases/tag/v1.7.0) [Compare Source](https://togithub.com/fsnotify/fsnotify/compare/v1.6.0...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. - 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. [#371]: https://togithub.com/fsnotify/fsnotify/pull/371 [#516]: https://togithub.com/fsnotify/fsnotify/pull/516 [#518]: https://togithub.com/fsnotify/fsnotify/pull/518 [#520]: https://togithub.com/fsnotify/fsnotify/pull/520 [#521]: https://togithub.com/fsnotify/fsnotify/pull/521 [#524]: https://togithub.com/fsnotify/fsnotify/pull/524 [#525]: https://togithub.com/fsnotify/fsnotify/pull/525 [#526]: https://togithub.com/fsnotify/fsnotify/pull/526 [#528]: https://togithub.com/fsnotify/fsnotify/pull/528 [#537]: https://togithub.com/fsnotify/fsnotify/pull/537 [#550]: https://togithub.com/fsnotify/fsnotify/pull/550 [#572]: https://togithub.com/fsnotify/fsnotify/pull/572Configuration
đ 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.
This PR has been generated by Mend Renovate. View repository job log here.