Skip to content

feat: remove Sidekiq server configuration from payloads#768

Open
stympy wants to merge 2 commits intomasterfrom
claude/review-sidekiq-error-reporting-pvt2P
Open

feat: remove Sidekiq server configuration from payloads#768
stympy wants to merge 2 commits intomasterfrom
claude/review-sidekiq-error-reporting-pvt2P

Conversation

@stympy
Copy link
Member

@stympy stympy commented Jan 1, 2026

Remove extraction and transmission of Sidekiq server configuration (@options) from error payloads. This configuration data was:

  • Rarely useful for debugging individual job errors
  • Often very large (400+ lines with sidekiq-scheduler)
  • Mostly static server settings that don't help diagnose failures
  • Including Proc objects that couldn't serialize properly

All job-specific debugging info (parameters, class, queue, retry count, stack trace) is still captured.

Fixes #767

Remove extraction and transmission of Sidekiq server configuration
(@options) from error payloads. This configuration data was:

- Rarely useful for debugging individual job errors
- Often very large (400+ lines with sidekiq-scheduler)
- Mostly static server settings that don't help diagnose failures
- Including Proc objects that couldn't serialize properly

All job-specific debugging info (parameters, class, queue, retry
count, stack trace) is still captured.

Fixes #767
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the extraction and transmission of Sidekiq server configuration data from error payloads to address serialization issues and reduce payload size. The configuration data (extracted from @options instance variable) was rarely useful for debugging, often very large (400+ lines with sidekiq-scheduler), and contained non-serializable Proc objects.

  • Removes conditional logic that extracted @options from ::Sidekiq::Config for different Sidekiq versions
  • Retains all job-specific debugging information (parameters, class, queue, retry count, stack trace)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link

@henrik henrik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this!

Co-authored-by: Henrik Nyh <henrik@nyh.se>
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.

(Option to) ignore global Sidekiq config?

5 participants