forked from rarkins/lazygit-example
-
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.7.0 #27
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 }}
Could not load tags
Nothing to show
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
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
October 18, 2021 23:15
d866319
to
225504f
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.4.9
Update module github.com/fsnotify/fsnotify to v1.5.1
Oct 18, 2021
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
March 26, 2022 12:45
225504f
to
8dae66f
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.5.1
Update module github.com/fsnotify/fsnotify to v1.5.3
Apr 24, 2022
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
April 24, 2022 23:57
8dae66f
to
86794d4
Compare
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 03:05
86794d4
to
c87683a
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
September 25, 2022 12:56
c87683a
to
599c98d
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
November 20, 2022 20:12
599c98d
to
fdabdc5
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
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
March 23, 2023 19:26
fdabdc5
to
a0dd87d
Compare
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.6.0
Update module github.com/fsnotify/fsnotify to v1.6.0 - autoclosed
Apr 4, 2023
renovate
bot
changed the title
Update module github.com/fsnotify/fsnotify to v1.6.0 - autoclosed
Update module github.com/fsnotify/fsnotify to v1.6.0
Apr 4, 2023
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
August 22, 2023 23:50
a0dd87d
to
dc0b7aa
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
September 19, 2023 23:20
dc0b7aa
to
5f243cd
Compare
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 23, 2023
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
October 23, 2023 05:45
5f243cd
to
bce73e2
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
November 16, 2023 17:50
bce73e2
to
3503cfc
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
January 30, 2024 08:46
3503cfc
to
5239e34
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
February 26, 2024 05:54
5239e34
to
0736e7a
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
April 14, 2024 23:51
0736e7a
to
34b59bc
Compare
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
May 9, 2024 14:52
34b59bc
to
cffe043
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-fsnotify-fsnotify-1.x
branch
from
June 5, 2024 05:23
cffe043
to
05f360c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.4.7
->v1.7.0
Release Notes
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
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
v1.5.1
: Revert Add AddRaw to not follow symlinksCompare Source
#394
v1.5.0
: Add AddRaw which does not dereference symlinksCompare Source
AddRaw
method which does not follow symlinks when adding a watch #289v1.4.9
: Move example usage to the readmeCompare Source
v1.4.8
: Use close-on-execCompare Source
1d13583
)11844c0
)ab058b4
)4bf2d1f
)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 Mend Renovate. View repository job log here.