SidekiqScheduler::Manager enormous inspect output
eapache-opslevel opened this issue · comments
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:
module SidekiqScheduler
class Manager
def inspect
"SidekiqScheduler::Manager"
end
end
end
But there should probably be some debugging information included, and I don't know what values are worth logging here.