<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=383182) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Self managed customers are reporting the following sorts of errors on their instances, and they can also be observed on GitLab.com This will block the eventual upgrade to Sidekiq version 7 ``` Job arguments to Projects::GitGarbageCollectWorker 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. Job arguments to Wikis::GitGarbageCollectWorker 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. ``` Multiple workers are affected, and so multiple groups would be responsible for the fix. So I've raised https://gitlab.com/gitlab-org/gitlab/-/issues/383181 to act as the hub for all the workers I found, and I'm raising separate issues for each worker (and may have to guess which group is responsible for the worker) ### Steps to reproduce Check on gitlab.com - https://log.gprd.gitlab.net/goto/800d7080-6820-11ed-85ed-e7557b0a598c ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### 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 See error in description. ### 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 3d55ac97c8d ### Possible fixes One worker got fixed in %"15.1" - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89736+ From the [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351870): > It's sufficient to ensure that the hash data uses string keys. <!-- If you can, link to the line of code that might be responsible for the problem. -->