You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2021. It is now read-only.
I'm creating an FSEvent notifier class and then calling start inside a thread ....
Thread.new { my_notifier.start }
My notifier is putting the list of changed directories into a queue to be picked up later by another thread. The problem is that the entire ruby interpreter halts; all other threads are suspended.
Not sure why this is happening. Is this the expected behavior?
TwP
The text was updated successfully, but these errors were encountered:
I wouldn't exactly say it's expected behavior. I actually never tried using this library in a threaded environment. I can confirm that when start the service in a thread, the ruby-interpreter blocks, waiting for the service to stop. Unfortunately, I don't know enough C to know how to fix it. Sorry this is blocking you (pun intended).
Hah I get this same issue just in irb when doing
require 'fsevent'
It will not return from that... :(
TwP -- sadly, this means that your fsevent branch of directory_watcher is unusable for me.
Using ruby-fsevent on ruby 1.8.7p174
I'm creating an FSEvent notifier class and then calling start inside a thread ....
Thread.new { my_notifier.start }
My notifier is putting the list of changed directories into a queue to be picked up later by another thread. The problem is that the entire ruby interpreter halts; all other threads are suspended.
Not sure why this is happening. Is this the expected behavior?
TwP
The text was updated successfully, but these errors were encountered: