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
Describe the bug
when perform as required arguments, sidekiq normally returns an error when calling perform_async without any arguments, this is no longer the case with sidekiq_unique_jobs 6.0.6
Expected behavior
the ArgumentError should be raised in the process calling perform_async
Current behavior
jobs is sent to sidekiq to crash.
Worker class
classMyWorkerincludeSidekiq::Workersidekiq_optionslock: :until_executed,queue: :undefaultdefperform(args);enddefself.unique_args(args)# the way you consider unique argumentsendend
The text was updated successfully, but these errors were encountered:
Sidekiq never had that behavior. perform_async doesn't raise ArgumentError, even when called with a different number of arguments. The error actually occurs when the job is executed and perform is called.
Describe the bug
when perform as required arguments, sidekiq normally returns an error when calling
perform_async
without any arguments, this is no longer the case with sidekiq_unique_jobs 6.0.6Expected behavior
the
ArgumentError
should be raised in the process callingperform_async
Current behavior
jobs is sent to sidekiq to crash.
Worker class
The text was updated successfully, but these errors were encountered: