You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Sidekiq.option was passed on Sidekiq 6.5.0+ as config, Sidekiq::BasicFetch#bulk_requeue will crash.
Because it call logger.debug and the logger is implemented as config.logger at Sidekiq::Component.
Conclusion
Sidekiq::LimitFetch#bulk_requeue also should not pass Sidekiq.options but Sidekiq to a argument of Sidekiq::BasicFetch.new fot Sidekiq 6.5.0+.
I think it should be like this:
After upgrading to Sidekiq 6.5.0+, we got the following error at
Sidekiq::Component#logger
.This is why
Sidekiq::LimitFetch#bulk_requeue
passesSidekiq.options
toSidekiq::BasicFetch.new
.sidekiq-limit_fetch/lib/sidekiq/limit_fetch.rb
Line 37 in 9655f7b
Sidekiq 6.5.0+ expects not
Sidekiq.options
butSidekiq
asconfig
and it is treated bySidekiq::Component
module. You can also see it at Sidekiq::CLI class.https://github.com/mperham/sidekiq/blob/e830ecd7ac1539877de03e57fb4807765f5fa392/lib/sidekiq/cli.rb#L25
If
Sidekiq.option
was passed on Sidekiq 6.5.0+ asconfig
,Sidekiq::BasicFetch#bulk_requeue
will crash.Because it call
logger.debug
and thelogger
is implemented asconfig.logger
atSidekiq::Component
.Conclusion
Sidekiq::LimitFetch#bulk_requeue
also should not passSidekiq.options
butSidekiq
to a argument ofSidekiq::BasicFetch.new
fot Sidekiq 6.5.0+.I think it should be like this:
The text was updated successfully, but these errors were encountered: