-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Warning in Ruby 3.0 #113
Comments
Hey @thomasklemm, thank you for reporting this issue! Do you have a clue how that should look like in Ruby 3? To be honest I don't fully grok what needs to be changed in order to be ready for Ruby 3. The code was introduced in #96. Maybe @hopsoft can expand on it. |
It looks like the warning gets raised since Edit: Edit 2: Looks like the proc holding a reference to |
This might be a solution : https://www.mikeperham.com/2010/02/24/the-trouble-with-ruby-finalizers/ |
@thomasklemm could you try out the https://github.com/hopsoft/cable_ready/tree/hopsoft/finalize branch from #116 and confirm that it addresses the issues you've seen? |
* Setup better finalizer SEE: https://www.mikeperham.com/2010/02/24/the-trouble-with-ruby-finalizers/ Resolves #113 * Add some defensive programming
* Setup better finalizer SEE: https://www.mikeperham.com/2010/02/24/the-trouble-with-ruby-finalizers/ Resolves stimulusreflex#113 * Add some defensive programming
* Setup better finalizer SEE: https://www.mikeperham.com/2010/02/24/the-trouble-with-ruby-finalizers/ Resolves stimulusreflex#113 * Add some defensive programming
After upgrading to Ruby 3.0, the following warning gets printed when running system specs right before the first reflex invocation in a spec example:
Link to the line in question.
The text was updated successfully, but these errors were encountered: