-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Einhorn incompatible with ruby 3.1 / psych 4 #5400
Comments
It looks like if I upgraded psych from 4.0.3 to 4.0.4 that would probably fix it (ruby/psych#539). I'll try tomorrow & report back... [EDIT: actually, scratch that - even with that pull request, 4.0.4 has safe loading by default. https://github.com/ruby/psych/pull/487 ] |
I believe they need to switch to safe_load and whitelist the Set class as Sidekiq does here with Symbol: If they do that, all should work. If no one else is willing to maintain it, I will need to fork it and start my own version. |
@mperham For what it's worth, Stripe appears to have deprecated the project - https://github.com/stripe-archive/einhorn |
I know, that’s why I just asked for new maintainers on Twitter. I’ll fork if I can’t get official blessing. |
Ruby version: 3.1.2
Rails version: 7.0.3
Sidekiq / Pro / Enterprise version(s): 6.5.1
I appreciate this isn't sidekiq's fault, but given that Einhorn is the officially recommended solution for rolling restarts in Sidekiq Enterprise, I was hoping to get some suggestions on how to deal with it...
We're in the middle of upgrading a ruby 3.0 installation to 3.1, which comes with Psych 4.
Einhorn successfully starts up in 3.1, but if you then try to reload it (
einhornsh --execute upgrade
), I get this output -Replacing YAML.load here with YAML.unsafe_load seems to work ok - there's a few other YAML.loads in the codebase, but AFAICT they're not trying to load any instances of
Set
.Has anyone else run into this?
The text was updated successfully, but these errors were encountered: