cloud-provider-azure

cloud-provider-azure copied to clipboard

Sourced from github.com/fsnotify/fsnotify's releases.

v1.6.0

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() and Op.Has() (#477)

  This makes checking events a lot easier; for example:

  if event.Op&Write == Write && !(event.Op&Remove == Remove) {
  }
  

  Becomes:

  if event.Has(Write) && !event.Has(Remove) {
  }
  

• 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 when Remove() is called on a path that's not 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)

... (truncated)

Sourced from github.com/fsnotify/fsnotify's changelog.

[1.6.0] - 2022-10-13

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() and Op.Has() (#477)

  This makes checking events a lot easier; for example:

  if event.Op&Write == Write && !(event.Op&Remove == Remove) {
  }
  

  Becomes:

  if event.Has(Write) && !event.Has(Remove) {
  }
  

• 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 when Remove() is called on a path that's not 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)

... (truncated)

• 5f8c606 Update ChangeLog
• 8878587 Tweak the docs a bit
• 89b4cf1 Add test for re-adding a renamed file (#508)
• 85acde2 Update x/sys
• 69c24b0 Update x/sys
• fb07f82 Add test to see what happens if you watch a symlink (#498)
• 666da9c Clarify doc comment on WatchList() (#499)
• 123e4e3 Add note about README version
• 61a05ce Update documentation and examples (#496)
• e180a87 Move some inotify-tests to run on all backends; test that state is cleaned up...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

In response to this:

/override "License Compliance "

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

In response to this:

/override "License Compliance"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

In response to this:

/override "tide"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.