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 used together with sidekiq-cron, the hashes may include _aj_symbol_keys keys which then confuses unique_arg method.
Expected behavior
The job to be executed.
Current behavior
The job was created. I can see the unique digest is created and also sidekiq-status creates initial record in Redis, BUT the job is NOT executed.
The unique digest is not removed however no job is running and it looks like nothing else happened.
Worker class
classMyWorkerincludeSidekiq::WorkerincludeSidekiq::Status::Workersidekiq_optionsretry: 0,lock: :until_executed,lock_expiration: 15.minutes.to_i,queue: :system_schedulersdefself.unique_args(args)# Here I've noticed that the there is `args.first['params']['_aj_symbol_keys']`argsenddefperform(args)# args['sleep'] == '10'# args['params'] == { foo1: 'bar1', foo2: 'bar2' }endend
I don't plan on supporting ActiveJob at all. Neither sidekiq-status nor sidekiq-cron has anything to do with the _aj_symbol_keys. That is all ActiveJob and I strongly recommend you stop using it and start using Sidekiq directly. In your example you don't even use ApplicationJob or ActiveJob::Base anywhere so I really don't see why you are using ActiveJob at all. Use MyWorker.perform_async instead of MyWorker.perform_later.
Describe the bug
When used together with sidekiq-cron, the hashes may include
_aj_symbol_keys
keys which then confusesunique_arg
method.Expected behavior
The job to be executed.
Current behavior
The job was created. I can see the unique digest is created and also sidekiq-status creates initial record in Redis, BUT the job is NOT executed.
The unique digest is not removed however no job is running and it looks like nothing else happened.
Worker class
Additional context
I think unique_jobs should try to
ActiveJob::Arguments.deserialize
args before using them.The text was updated successfully, but these errors were encountered: