-
Notifications
You must be signed in to change notification settings - Fork 37
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
IPAddr#freeze
is broken
#35
Comments
IMO this is a valid use case meaning the bug should be fixed. I went ahead and got a proposal to patch it here: #36 |
Thanks for this, feel free to close this issue if this was the only case where it was broken. Thanks! |
Hello, I met this issue in ruby-3.1 release.
I can temporarily solve it by putting this line at my gemfile
|
I don't know why this isn't synchronised. |
https://bugs.ruby-lang.org/issues/18570 now in ruby 3.1.1 I have upgraded my application and verified it works
|
ipaddr-1.2.4 is contained 3.1.1. |
After freezing
IPAddr
instance, a lot of methods die withFrozenError: can't modify frozen IPAddr
.It seems that
clone.set()
in these methods should beclone(freeze: false).set()
ordup.set()
The text was updated successfully, but these errors were encountered: