-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update module github.com/fsnotify/fsnotify to v1.8.0 #103
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/github.com-fsnotify-fsnotify-1.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #103 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 13 13
Lines 200 200
=========================================
Hits 200 200
Flags with carried forward coverage won't be shown. Click here to find out more. |
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.5.3
Update module github.com/fsnotify/fsnotify to v1.5.4
May 16, 2022
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
May 16, 2022 02:28
303cf48
to
f9c8ca3
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
November 20, 2022 13:20
f9c8ca3
to
43cab8f
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.5.4
Update module github.com/fsnotify/fsnotify to v1.6.0
Nov 20, 2022
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.6.0
Update module github.com/fsnotify/fsnotify to v1.7.0
Oct 22, 2023
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
October 22, 2023 09:13
43cab8f
to
ba328e8
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0
Update module github.com/fsnotify/fsnotify to v1.7.0 - autoclosed
Oct 23, 2023
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0 - autoclosed
Update module github.com/fsnotify/fsnotify to v1.7.0
Oct 23, 2023
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
October 23, 2023 14:25
ba328e8
to
8dbf148
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0
Update module github.com/fsnotify/fsnotify to v1.7.0 - autoclosed
Oct 27, 2024
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0 - autoclosed
Update module github.com/fsnotify/fsnotify to v1.7.0
Oct 27, 2024
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
October 27, 2024 10:16
8dbf148
to
566b55a
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0
Update module github.com/fsnotify/fsnotify to v1.7.0 - autoclosed
Oct 31, 2024
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0 - autoclosed
Update module github.com/fsnotify/fsnotify to v1.7.0
Oct 31, 2024
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
October 31, 2024 12:40
566b55a
to
62e277b
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.7.0
Update module github.com/fsnotify/fsnotify to v1.8.0
Oct 31, 2024
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.8.0
Update module github.com/fsnotify/fsnotify to v1.8.0 - autoclosed
Dec 12, 2024
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.8.0 - autoclosed
Update module github.com/fsnotify/fsnotify to v1.8.0
Dec 12, 2024
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
December 12, 2024 16:55
6a0a4f1
to
62e277b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.1
->v1.8.0
Release Notes
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
v1.8.0
Compare Source
Additions
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 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_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
onAdd()
when the watcher is closed (#516)other: add
Watcher.Errors
andWatcher.Events
to the no-opWatcher
inbackend_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 theappengine
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()
andOp.Has()
(#477)This makes checking events a lot easier; for example:
Becomes:
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
whenRemove()
is called on a path that'snot 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.
v1.5.4
Compare Source
What's Changed
New Contributors
Full Changelog: fsnotify/fsnotify@v1.5.2...v1.5.4
v1.5.3
Compare Source
v1.5.2
Compare Source
What's Changed
poller.fd
twice innewFdPoller
by @tklauser in https://github.com/fsnotify/fsnotify/pull/406New Contributors
Full Changelog: fsnotify/fsnotify@v1.5.1...v1.5.2
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 was generated by Mend Renovate. View the repository job log.