Skip to content

Cannot open Sidekiq morgue in mounted admin app because of job with invalid arguments #4095

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

Closed
Mange opened this issue Feb 8, 2019 · 1 comment

Comments

@Mange
Copy link

Mange commented Feb 8, 2019

Trying to open the morgue gives a 500 Internal Server Error. Underlying error is:

NoMethodError: undefined method `map' for "(...)":String
Did you mean?  tap
  from sidekiq/web/helpers.rb:210:in `display_args'
  from (eval):49:in `block in _erb_morgue'
  from (eval):34:in `each'
  from (eval):34:in `_erb_morgue'
  from sidekiq/web/action.rb:85:in `_erb'
  from sidekiq/web/action.rb:54:in `erb'
  from sidekiq/web/application.rb:111:in `block in <class:WebApplication>'
  from sidekiq/web/application.rb:287:in `instance_exec'
  from sidekiq/web/application.rb:287:in `block in call'
  from sidekiq/web/application.rb:283:in `catch'
  from sidekiq/web/application.rb:283:in `call'

Sidekiq 5.2.3

From reading the code at the point of failure, it looks like the arguments are a string instead of an array.


We don't think we've scheduled any jobs except through the official API, but until we can inspect the message we can't tell what it is.

Best-case would be some defensive fallback for the argument rendering so it's kept around, allowing us to investigate it.

I'd also be happy to just have a way to get rid of the offending message so I can get back the morgue.

Thank you for your time!


Extracted from #3389 (comment)

@mperham mperham closed this as completed in d911036 Feb 8, 2019
@mperham
Copy link
Collaborator

mperham commented Feb 8, 2019

Issue should be fixed, you are welcome to pull master and verify for your case.

gearnode pushed a commit to gearnode/sidekiq that referenced this issue Feb 28, 2019

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
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

No branches or pull requests

2 participants