Potential blockers for Sidekiq 7.0 upgrade - Job arguments to <workername> do not serialize to JSON safely.
Summary
Multiple jobs are generating the warning:
Job arguments to <workername> do not serialize to JSON safely. This will raise an error in
Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
by calling `Sidekiq.strict_args!` during Sidekiq initialization.There's a couple of existing issues for specific jobs, and multiple reports from customers for different workers.
As each worker will require effort by different teams, I'll open a bunch of issues for those teams and relate them all to this issue.
Steps to reproduce
Check on gitlab.com - https://log.gprd.gitlab.net/goto/800d7080-6820-11ed-85ed-e7557b0a598c
Example Project
What is the current bug behavior?
Sidekiq generates the error based on arguments to the worker.
What is the expected correct behavior?
Sidekiq no longer generates the error.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com.
Log entries for this class of issue can be found at: https://log.gprd.gitlab.net/goto/800d7080-6820-11ed-85ed-e7557b0a598c
GitLab Enterprise Edition 15.6.0-pre 3d55ac97
Possible fixes
One worker got fixed in %15.1 - Fix Sidekiq warning in Gitlab::EventStore (!89736 - merged)
From the issue:
It's sufficient to ensure that the hash data uses string keys.