roundhouse_ui 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 46c3254f820732cc242a9bdc774b2361dfadef7b2b1256f149d3d69c07f1be1b
-  data.tar.gz: 7037fdc482c7d515bd3168754f445ed046d0f26e53340014a29dd2c0591ae9d0
+  metadata.gz: 55d676d5630bc1696fd0c44d58494a84263d53c340ceffeb1bc44c04c9201dfa
+  data.tar.gz: b314d38079f0f8eee84ba9052dd781841fd6dba2fc7f612e82d25466b5c62c9f
 SHA512:
-  metadata.gz: 80c1574f244bf2f4f4782811aa3688029421d6e06079aa693690da97f056b80a019ced7306ba7ee5d0e83122d53401a1135070ba2ea1a63c30a2491a4e1b7e83
-  data.tar.gz: 28da55ba898c4eabfb2bca7a33f2f3d6524fdfde833ca2d3cf792ce37fd3d3b2720c5a98a27f2a73ed79424019f2339a09423853a14604920c9e0f89230acfac
+  metadata.gz: 0454ea6d65176e5d5c79893dc52982e985231ff51f6e503624f7d19af60beabec808ced45cc27a2cd3c2021044e5b6d5d7c1bdf26193ef98833a27e6faaad17f
+  data.tar.gz: 1aa6b74df3071ced45e118dda22aa0d0caadc17a10fd64c4dec45c187dc7d68866e8e417529a6ad424dc467960481a7187de908283e4dc7932c2977ea047e70c

data/README.md

@@ -79,9 +79,17 @@ RoundhouseUi.configure do |c|
 
   # Where queue snapshots are stored (default: Redis). Swap for a file/S3 store.
   # c.snapshot_store = MyS3SnapshotStore.new
+
+  # Fold sidekiq-failures' `failed` set into the Errors view (see below).
+  # No-op unless the sidekiq-failures gem is loaded. Default: off.
+  c.show_sidekiq_failures = true
 end
 ```
 
+Every option is independent and has a safe default — set only what you need.
+`read_only`, `allow_job_editing`, and `show_sidekiq_failures` default to `false`;
+`redact_args` to `[]`; `observability` to a no-op adapter; `snapshot_store` to Redis.
+
 ## Pausing queues
 
 Pause/resume is pure OSS. To make a pause actually stop a queue from being worked,
@@ -99,6 +107,27 @@ all of Sidekiq's weighting/ordering. Until it's installed, the Queues page recor
 but **warns that they aren't enforced** (worker and web are separate processes, so
 Roundhouse detects whether a fetcher has reported in).
 
+> ⚠️ **Sidekiq Pro/Enterprise users:** super_fetch / reliable fetch sets its own
+> `fetch_class`, and Sidekiq allows only one. Installing `RoundhouseUi::Fetch` would
+> **replace reliable fetch and lose its crash-recovery guarantees** — don't. On those
+> tiers, leave the fetch strategy out; pause/resume stays inert and the UI says so.
+
+## Surfacing sidekiq-failures
+
+If you use [`sidekiq-failures`](https://github.com/mhfs/sidekiq-failures), failures it
+records live in their own Redis set — which Roundhouse doesn't read by default. Jobs with
+`retry: false` are the common case: they fail, get recorded there, but never enter the
+retry or dead sets, so they're invisible in Roundhouse. Opt in to fold them into the
+grouped **Errors** view:
+
+```ruby
+# config/initializers/roundhouse.rb
+RoundhouseUi.configure { |c| c.show_sidekiq_failures = true }
+```
+
+It's a no-op unless `sidekiq-failures` is loaded. Failures appear in **Errors** grouped by
+job class + error (not yet as an individual-job list with per-row actions).
+
 ## Cancelling jobs
 
 Cancellation is cooperative — Ruby can't safely kill a running thread. Install the

data/app/controllers/roundhouse_ui/errors_controller.rb

@@ -18,7 +18,7 @@ module RoundhouseUi
       scanned = 0
       truncated = false
 
-      { "retry" => Sidekiq::RetrySet.new, "dead" => Sidekiq::DeadSet.new }.each do |source, set|
+      sources.each do |source, set|
         set.each do |entry|
           scanned += 1
           if scanned > SCAN_LIMIT
@@ -35,6 +35,17 @@ module RoundhouseUi
       [ list, scanned, truncated ]
     end
 
+    # Sidekiq's native sets, plus the sidekiq-failures `failed` set when opted in
+    # and that gem is loaded. Its FailureSet is a Sidekiq::JobSet, so it iterates
+    # exactly like the others — no special-casing in the aggregation above.
+    def sources
+      sets = { "retry" => Sidekiq::RetrySet.new, "dead" => Sidekiq::DeadSet.new }
+      if RoundhouseUi.show_sidekiq_failures && defined?(Sidekiq::Failures::FailureSet)
+        sets["failed"] = Sidekiq::Failures::FailureSet.new
+      end
+      sets
+    end
+
     def record(groups, source, entry)
       error = entry.item["error_class"] || "UnknownError"
       group = (groups["#{entry.klass}|#{error}"] ||= {

data/lib/roundhouse_ui/version.rb

@@ -1,3 +1,3 @@
 module RoundhouseUi
-  VERSION = "0.2.0"
+  VERSION = "0.3.0"
 end

data/lib/roundhouse_ui.rb

@@ -51,6 +51,12 @@ module RoundhouseUi
     # e.g. RoundhouseUi.redact_args = %w[password token secret]. Default: none.
     attr_accessor :redact_args
 
+    # Opt-in: fold failures recorded by the `sidekiq-failures` gem (its `failed`
+    # sorted set) into the grouped Errors view. Off by default, and a no-op
+    # unless sidekiq-failures is loaded. Jobs with `retry: false` never enter
+    # Sidekiq's retry/dead sets, so this is the only way to surface them here.
+    attr_accessor :show_sidekiq_failures
+
     # Configure in an initializer:
     #
     #   RoundhouseUi.configure do |c|
@@ -70,4 +76,5 @@ module RoundhouseUi
   self.read_only = false
   self.allow_job_editing = false
   self.redact_args = []
+  self.show_sidekiq_failures = false
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: roundhouse_ui
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - R.J. Robinson
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-06-29 00:00:00.000000000 Z
+date: 2026-06-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails