-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Using rb-inotify within Async task #43
Comments
@brandonhilkert I'm happy to hear it's been super useful - if you have commercial use case please consider sponsoring a gem within the eco-system: https://github.com/socketry/community#funding Does The other option is to use a thread to run the So, my first suggestion is to check how we can integrate it better. |
I assume your comment here would be the idea, right? |
Yes, that's basically it.
|
Feel free to give me an update. We should add documentation to clarify this use case. |
In Async 2.x world, all IO is now non-blocking, so this should be a non-issue. Please try it out and open a new issue if you are still having problems. |
We're looking to use https://github.com/guard/rb-inotify as a wrapped class that will monitor a path on the filesystem and also invoke other work. We're seeing the monitor get blocked on startup of the Reactor.
Here's a simplified example
Would we have to use
rb-inotify
differently for it to be compatible with the reactor?BTW - the whole family of async gems have been incredibly helpful. Thanks so much for your time and effort on them!
The text was updated successfully, but these errors were encountered: