Closed albertski closed 1 year ago
Here is the diff, let me take a look at what might have changed: https://github.com/socketry/nio4r/compare/v2.5.9...v2.6.0
Do you mind updating the version of Ruby to 3.2.2 and the version of Puma to check if the issue still exists?
There was a slight behavioural change here: https://github.com/socketry/nio4r/compare/v2.5.9...v2.6.0#diff-bce1c1b7cb30fa881da1ad53c13dcff2903d61028874c65f6354b2258f17a0edL100-R112
The io
that gets stored is the result of to_io
- I can revert this. It's the only thing I can think may affect the code.
Are you able to test with this branch? https://github.com/socketry/nio4r/pull/306
Thanks @ioquatix. I confirm that by upgrading Puma to 6.0.2, the issue went away. Also, I confirm https://github.com/socketry/nio4r/pull/306 fixed the issue too (with Puma 4.3.12). Thanks for the quick fix.
Released in v2.6.1.
After upgrading nio4r, I get the following error on CircleCi:
I'm using nio4r on a Rails 6 project using Ruby 3.0.3. Puma is a 4.3.12. Would you have any insight why this is happening?