rb-fsevent 0.10.2 → 0.10.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 61d076a09964b861d80f4724752654bd1e03d7b1
-  data.tar.gz: 549a175bc931f6e247d09e87bc4a0e805a8715b8
+  metadata.gz: 75179745011638e7c72f22fd0176a2d7d1e05dac
+  data.tar.gz: d41968eb7b74fc36e874c3d19e8b8b684d5cfc66
 SHA512:
-  metadata.gz: e124acb15e091aae6d754e00dde77dde57a267c3c209cab827735f527abce5800d4b16066adaeacdbadc4fa8311b1622bda29bf300de8a1a4c3c4d1033e7f1d4
-  data.tar.gz: d27912bb5ea1822547af03aeabb819a6aabf39b1cae25289e0132ac768d68d7751f1895ccd97bdbf9026c2c1fe787d8d0612708a725fcef6c9882fa4a91e1082
+  metadata.gz: cc6d47ae4861f428d889a2ee76b9d2baa8e80ecc5a5fcb032804d8552899f091352b15ba722ea7cf88174471bfc93f765a1f1a92b90c16dab92f102b2867fe8b
+  data.tar.gz: 99feafaa005aebf50d9907d5ddddd2518062d9db6d8a61e9890023be661ce8c9a68ffbaa1a2a4babe23604b004dfc11495d856d6f3dcf28a0291a2a9b14f92ca

data/README.md

@@ -5,17 +5,18 @@
 
 Very simple & usable Mac OSX FSEvents API
 
-* RubyCocoa not required!
 * Signals are working (really)
 * Tested on MRI 2.4.1, RBX 3.72, JRuby 1.7.26 and 9.1.8.0
 * Tested on 10.8
 
 ## HFS+ filename corruption bug
 
-There is a _very_ long-standing (since 2011) OSX bug where sometimes the filename metadata for HFS+ filesystems will get corrupted, resulting in some APIs returning one case for a file, and other APIs returning another. This corruption is not currently fixed by their tools, though Apple has been made aware of the issue and are working on it (as of may 2015). The result is that sometimes, _for no visible reason to the user_, fsevents would simply not work. As of rb-fsevent 0.9.5 this issue is properly detected and an insanely hacky (but effective) workaround is used that replaces the system `realpath()` with a custom implementation that should always return the same value as the kernel reporting (thus fixing fsevents).
+There is a _very_ long-standing (since 2011) OSX bug where sometimes the filename metadata for HFS+ filesystems will get corrupted, resulting in some APIs returning one case for a file, and other APIs returning another. The result is that sometimes, _for no visible reason to the user_, fsevents would simply not work. As of rb-fsevent 0.9.5 this issue is properly detected and an insanely hacky (but effective) workaround is used that replaces the system `realpath()` with a custom implementation that should almost always return the same value as the kernel reporting (thus fixing fsevents). The major flaw in the workaround is that it may return the wrong path for hard links.
 
 Please note that this doesn't repair the underlying issue on disk. Other apps and libraries using fsevents will continue to break with no warning. There may be other issues unrelated to fsevents.
 
+__This bug is resolved in MacOS 10.12 and all users are strongly encouraged to upgrade.__
+
 ## Install
 
     gem install rb-fsevent

data/lib/rb-fsevent/fsevent.rb

@@ -52,7 +52,7 @@ class FSEvent
       found_length = false
 
       while reading_length
-        byte = @pipe.read(1)
+        byte = @pipe.read_nonblock(1)
         if "#{byte}" =~ /\d/
           length << byte
           found_length = true

data/lib/rb-fsevent/version.rb

@@ -1,5 +1,5 @@
 # -*- encoding: utf-8 -*-
 
 class FSEvent
-  VERSION = '0.10.2'
+  VERSION = '0.10.3'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rb-fsevent
 version: !ruby/object:Gem::Version
-  version: 0.10.2
+  version: 0.10.3
 platform: ruby
 authors:
 - Thibaud Guillaume-Gentil
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-07-01 00:00:00.000000000 Z
+date: 2018-03-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -123,7 +123,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.11
+rubygems_version: 2.6.13
 signing_key: 
 specification_version: 4
 summary: Very simple & usable FSEvents API