Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Sidekiq warnings about JSON serialization #17381

Merged
merged 2 commits into from
Jan 27, 2022

Conversation

ClearlyClaire
Copy link
Contributor

This occurs on every symbol argument we pass, and every symbol key in hashes, because Sidekiq expects strings instead.

See sidekiq/sidekiq#5071

We do not need to change how workers parse their arguments because this has not changed and we were already converting to symbols adequately or using with_indifferent_access.

This occurs on every symbol argument we pass, and every symbol key in hashes,
because Sidekiq expects strings instead.

See sidekiq/sidekiq#5071

We do not need to change how workers parse their arguments because this has
not changed and we were already converting to symbols adequately or using
`with_indifferent_access`.
In order to more easily catch issues that would produce warnings in production
code.
@ClearlyClaire ClearlyClaire marked this pull request as ready for review January 26, 2022 23:26
@Gargron Gargron merged commit 03d5934 into mastodon:main Jan 27, 2022
jesseplusplus pushed a commit to jesseplusplus/decodon that referenced this pull request Feb 10, 2022
* Fix Sidekiq warnings about JSON serialization

This occurs on every symbol argument we pass, and every symbol key in hashes,
because Sidekiq expects strings instead.

See sidekiq/sidekiq#5071

We do not need to change how workers parse their arguments because this has
not changed and we were already converting to symbols adequately or using
`with_indifferent_access`.

* Set Sidekiq to raise on unsafe arguments in test mode

In order to more easily catch issues that would produce warnings in production
code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants