sidekiq
sidekiq copied to clipboard
sidekiq
Simple, efficient background processing for Ruby
Several people have asked for better/deeper integration with instrumentation like ActiveSupport's notifications. Things which are log warnings today could be emitted as notifications, which are more flexible in where they...
## Background While Sidekiq Web UI has used Boostrap 3.3.7 since #3117 (2016; 8 years ago), 5 years passed after the EOL of Bootstrap 3. > Bootstrap 3 reached end...
# Bug description When registering a Periodic job with the cron expression `0/30 * * * *` (which is invalid) Sidekiq initializes normally, but the Periodic Jobs functionality does not...
Ruby version: 3.3.0 Rails version: 7.1.3.4 Sidekiq / Pro / Enterprise version(s): 7.3.1 In my application i've discovered an issue where inside of a batch, when I go to reopen...
I couldn't find a canonical best practice on how to deal with (what I believe is) a common need: handling transient external API errors without needlessly notifying my error monitoring...
Several customers have asked for support for basic composition with rate limiters, e.g. (limit1 AND limit2 AND limit3). Imagine a scenario where a service has an official rate limit of...
The cron and unique subsystems both use SHA1 today. The algorithm is increasingly outdated and it's likely that things like FIPS 140-3 will forbid its use globally, even if not...
Per https://github.com/sidekiq/sidekiq/blob/v8.0.4/lib/sidekiq/job_retry.rb#L258-L265 A job with ```ruby sidekiq_retries_exhausted do |_job, _ex| :discard end ``` Will skip the morgue, and will _not_ invoke its death handlers. While a job configured simply with...
Continued from https://github.com/sidekiq/sidekiq/pull/6712. Example config: ```ruby Sidekiq.configure_server do |config| config.flavor_with(:active_job) # ... end Sidekiq.configure_client do |config| config.flavor_with(:active_job) # ... end ```
