-
-
Notifications
You must be signed in to change notification settings - Fork 890
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 x/sys to latest #379
Conversation
It looks that Go 1.11 support on darwin was dropped by https://go-review.googlesource.com/c/sys/+/250437 I think we should drop support for Go 1.11 because the release policy of Go https://tip.golang.org/doc/devel/release#policy says "Each major Go release is supported until there are two newer major releases". |
Shall I update this PR to include an update to the test matrix? Should 1.11 just be dropped entirely? Should any other releases be dropped at the same time? |
In my opinion, I recommend to create a pull request that drops Go 1.11. But, I'm a newbie in fsnotify org. |
Done. See #381 |
* introduce GitHub Actions * Add lint+vet+old versions to GitHub Action * Remove Travis CI and references * Drop support/testing for Go 1.11 and earlier (fsnotify#381) * Update x/sys to latest (fsnotify#379) * add //go:build lines + add 1.17.0-rc2 to test matrix (fsnotify#377) * Update test matrix for go 1.17 stable release (fsnotify#385) * Add AddRaw to not follow symlinks + Fix link folloing on Windows (fsnotify#289) * v1.5.0 preparation (fsnotify#380) * revise pull request template * Revert "Add AddRaw to not follow symlinks + Fix link folloing on Windows (fsnotify#289)" This reverts commit e2e9517. * prepare 1.5.1, retract 1.5.0 * Removed dead link * Update issue templates (fsnotify#410) * Update issue templates * remove old issue template * Test on Go 1.18 and two most recent versions (fsnotify#411) * Test on Go 1.18 and two most recent versions * on push * ci * update readme * revise contributing * maintainers wanted * Final Notice: Maintainers Wanted * fix go vet warnings: call to (*T).Fatalf from a non-test goroutine (fsnotify#416) * made the changes related to recursive directory check * made changes in window.go for buffer size * DA-992: Pair windows' delete + create event to generate a rename event (#1) * made the changes related to recursive directory check * made changes in window.go for buffer size * added the oldname attribute * old name added to rename event, one event is generated for rename * added oldname in printing rename events * tests for checking the oldName attr for rename added * create fsnotify event added * input to create event changed * create fsnotify event function modified * ID added * logs added * added create fsnotify event in inotify * logs added * prints added * reviews * reviews addressed * Hangkun/da 992/window rename event (#2) * Let's begin * Add getpath * Init test workflow * 1.40.0 exits? * Linter fix * asdf * 100 Co-authored-by: hu13 <hangkun@preveil.com> * Clean up unused * Badge Co-authored-by: Hangkun Ung <hangkun.ung@gmail.com> Co-authored-by: hu13 <hangkun@preveil.com> * Rebase upstream fixes * Rename bundle only works on windows * Update CI golang Co-authored-by: Ichinose Shogo <shogo82148@gmail.com> Co-authored-by: Oliver Bristow <evilumbrella+github@gmail.com> Co-authored-by: Nahum Shalman <nahamu@gmail.com> Co-authored-by: Nathan Youngman <4566+nathany@users.noreply.github.com> Co-authored-by: Loïc Vernet <vernet.loic@gmail.com> Co-authored-by: Nathan Youngman <git@nathany.com> Co-authored-by: paris <pariya.b@gmail.com> Co-authored-by: hu13 <hangkun@preveil.com>
What does this pull request do?
Upgrades x/sys to the latest revision as of today.
Where should the reviewer start?
This update appears to break test
(macos-latest, 1.11)
.#371 will require an update to x/sys and exhibits the same test failure.
This PR demonstrates that the breakage is from x/sys, not the content of #371.
I don't know if it's safe to drop support for 1.11, if this represents a bug somehow introduced into x/sys/unix, or something else.
How should this be manually tested?
The important test failure is automated with GitHub actions.