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
Given a sidekiq job where parts of the first argument are user input, the determination of the actual job class fails if the argument contains job_class as a substring.
For example:
["{\"user_id\":1,\"user_input\":[{\"name\":\"John Doe\",\"message\":\"This is a test message with job_class\"}]}
So if the first job argument contains the substring job_class it will return it as a string.
Given a sidekiq job where parts of the first argument are user input, the determination of the actual job class fails if the argument contains
job_class
as a substring.For example:
So if the first job argument contains the substring
job_class
it will return it as a string.See https://github.com/kenaniah/sidekiq-status/blob/main/lib/sidekiq-status/client_middleware.rb#L25
I suppose using the worker_class first could solve the problem.
This is the error I was getting:
The text was updated successfully, but these errors were encountered: