Skip to content

Commit

Permalink
Remove EventedFileUpdateChecker#updated? caveat [ci-skip]
Browse files Browse the repository at this point in the history
Since #39718, `EventedFileUpdateChecker#updated?` no longer always
returns `true` after a fork.
  • Loading branch information
jonathanhefner committed Feb 21, 2022
1 parent 9dbf7a5 commit 0c6ea78
Showing 1 changed file with 0 additions and 2 deletions.
Expand Up @@ -17,8 +17,6 @@ module ActiveSupport
# EventedFileUpdateChecker#execute is run or when EventedFileUpdateChecker#execute_if_updated
# is run and there have been changes to the file system.
#
# Note: Forking will cause the first call to `updated?` to return `true`.
#
# Example:
#
# checker = ActiveSupport::EventedFileUpdateChecker.new(["/tmp/foo"]) { puts "changed" }
Expand Down

0 comments on commit 0c6ea78

Please sign in to comment.