Skip to content
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

Prepare for upcoming Sidekiq::Config redesign #5340

Merged
merged 8 commits into from
May 31, 2022
Merged

Prepare for upcoming Sidekiq::Config redesign #5340

merged 8 commits into from
May 31, 2022

Conversation

mperham
Copy link
Collaborator

@mperham mperham commented May 23, 2022

Adjust the server internals to use a config object rather than refering directly to the Sidekiq module.

@mperham mperham mentioned this pull request May 26, 2022
3 tasks
@mperham
Copy link
Collaborator Author

mperham commented May 26, 2022

For 6.x, Sidekiq::Components will be passed the Sidekiq module itself as a parameter. This will become a Sidekiq::Config instance in 7.0.

@mperham
Copy link
Collaborator Author

mperham commented May 30, 2022 via email

@mperham
Copy link
Collaborator Author

mperham commented May 30, 2022

Sorry, forgot tomorrow is a holiday. Tuesday!

@SamArdrey
Copy link
Contributor

SamArdrey commented May 30, 2022 via email

@TonsOfFun
Copy link

I'm interested in contributing to this implementation as well.

@mperham
Copy link
Collaborator Author

mperham commented May 31, 2022

@TonsOfFun I don't have a good process for collaborating on this.

@mperham mperham merged commit 67daa7a into main May 31, 2022
@mperham mperham deleted the remove_util branch May 31, 2022 20:37
@CvX
Copy link

CvX commented Jun 8, 2022

The removal of lib/sidekiq/exception_handler.rb was a breaking change, see: dependabot PR/CI failure

What is the recommended way to provide extra context to exceptions in Sidekiq 6.x?

In Discourse we've been using this:
https://github.com/discourse/discourse/blob/7fc11327b7a137351b9adb100cb89a61d7f8aa95/lib/discourse.rb#L12-L15
https://github.com/discourse/discourse/blob/7fc11327b7a137351b9adb100cb89a61d7f8aa95/lib/discourse.rb#L167-L180

@mperham
Copy link
Collaborator Author

mperham commented Jun 8, 2022

@CvX Please do not litter closed issues with your own problems. Open your own issue. I would be happy to help.

st0012 added a commit to getsentry/sentry-ruby that referenced this pull request Jun 18, 2022
Sidekiq starts to store/pass configurations differently, which doesn't
affect the SDK itself. But we need to update the test setup accordingly.

Related PR:sidekiq/sidekiq#5340
st0012 added a commit to getsentry/sentry-ruby that referenced this pull request Jun 18, 2022
Sidekiq starts to store/pass configurations differently, which doesn't
affect the SDK itself. But we need to update the test setup accordingly.

Related PR:sidekiq/sidekiq#5340
st0012 added a commit to getsentry/sentry-ruby that referenced this pull request Jun 18, 2022
Sidekiq starts to store/pass configurations differently, which doesn't
affect the SDK itself. But we need to update the test setup accordingly.

Related PR:sidekiq/sidekiq#5340
st0012 added a commit to getsentry/sentry-ruby that referenced this pull request Jun 18, 2022
Sidekiq starts to store/pass configurations differently, which doesn't
affect the SDK itself. But we need to update the test setup accordingly.

Related PR:sidekiq/sidekiq#5340
anero added a commit to controlshift/sidekiq-rate-limiter that referenced this pull request Jul 28, 2022
anero added a commit to controlshift/sidekiq-rate-limiter that referenced this pull request Jul 28, 2022
anero added a commit to controlshift/sidekiq-rate-limiter that referenced this pull request Jul 28, 2022
vishalzambre added a commit to vishalzambre/sidekiq-cloudwatchmetrics that referenced this pull request Jul 29, 2022
@jpcamara jpcamara mentioned this pull request Aug 11, 2022
11 tasks
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.

None yet

4 participants