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
Trying to inspect an instance of SidekiqScheduler::Manager produces around 5k lines of output on our system because it holds references to a bunch of other complex objects and eventually starts printing large chunks of internal sidekiq and rails objects.
This is doubly annoying because with debug-logging enabled on sidekiq, the SidekiqScheduler::Manager instance is inspected/logged at sidekiq startup.
It's easy enough to monkey-patch with something like:
I am not able to share this output, as the resulting dump of ruby objects includes a great deal of sensitive information about our code base, including e.g. our redis password. It is 2MB of text, so it is too large for me to manually redact all the sensitive information.
You should be able to reproduce for yourself by running bundle exec sidekiq -v on a sidekiq setup with sidekiq-scheduler. Any sidekiq version after 7.0.7 (sidekiq/sidekiq#5822 is required) should print the config object when started with -v and will thus trigger the inspect of the scheduler-manager.
Trying to inspect an instance of
SidekiqScheduler::Manager
produces around 5k lines of output on our system because it holds references to a bunch of other complex objects and eventually starts printing large chunks of internal sidekiq and rails objects.This is doubly annoying because with debug-logging enabled on sidekiq, the
SidekiqScheduler::Manager
instance is inspected/logged at sidekiq startup.It's easy enough to monkey-patch with something like:
But there should probably be some debugging information included, and I don't know what values are worth logging here.
The text was updated successfully, but these errors were encountered: