fix(deps): update module github.com/fsnotify/fsnotify to v1.8.0 #2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/github.com-fsnotify-fsnotify-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.6.0->v1.8.0Release Notes
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
v1.8.0Compare Source
Additions
FSNOTIFY_DEBUGto 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.0Compare 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 toAdd()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_MODIFIEDby 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
ErrEventOverflowif 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
ErrClosedonAdd()when the watcher is closed (#516)other: add
Watcher.ErrorsandWatcher.Eventsto the no-opWatcherinbackend_other.go, making it easier to use on unsupported platforms such as WASM, AIX, etc. (#528)other: use the
backend_other.gono-op if theappenginebuild tag is set; Google AppEngine forbids usage of the unsafe package so the inotify backend won't compile there.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.
This PR has been generated by Renovate Bot.
ℹ Artifact update notice
File name: src/go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):Details:
golang.org/x/sysv0.10.0->v0.13.0Checkout
From your project repository, check out a new branch and test the changes.