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
Keyword argument support in v6.4.0 breaks for jobs enqueued before v6.4.0 #5138
Comments
Paging @4e4c52 |
Fixed in #5142 |
mperham
pushed a commit
that referenced
this issue
Jan 24, 2022
mperham
added a commit
that referenced
this issue
Jan 31, 2022
Any word on when a 6.4.1 release might land? 6.4.0 resolves a (minor, for us) CVE, but we can't safely adopt it without this change :-\ Edit: Never mind, just landed :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ruby version: 2.7.5
Rails version: 6.0.4.3
Sidekiq / Pro / Enterprise version(s): v6.4.0
It seems that this PR:
caused mails enqueued with Sidekiq versions before v6.4.0 to stop working and crash to this error:
I assume that this is because in here:
https://github.com/mperham/sidekiq/blob/34d081f4ed54873663e70dc1e2795d8646bfe15a/lib/sidekiq/extensions/action_mailer.rb#L18-L20
the code assumes that the incoming
yml
parameter contains four parameters and does not protect against the lastkwargs
parameter not being there in the first place.kwargs
isnil
when the DelayedMailer job has been enqueued on a version of Sidekiq prior to v6.4.0.I don't know if new versions of Sidekiq should make the jobs compatible with the previous version, so this might not be an issue worth of fixing. We were able to re-enqueue the one job we got stuck in the queue and remove the old one.
Initializer
The big thing in initializer is the enabling of
.delay
APIHere's the entire initializer for completeness sake:
We're currently in the process of cleaning up the middleware related tomfoolery that existed before we enabled Zeitwerk. That code should be irrelevant to this issue, though.
Backtrace:
The text was updated successfully, but these errors were encountered: