karafka-web 1.0.0.beta1 → 1.0.0.rc1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 27e32327bc795732ee58f5dc757bd1fbe1dbc24198a8561f67cffbb48c5a4eb3
-  data.tar.gz: 81bb5e628233f6acf7d9cf0527ed07517271cc87f4b19cef925dd2e4e3887ef0
+  metadata.gz: 64a1fc3668da51d60226e170e3942d77e9da1dc440d85a16e5678d0bb54ca592
+  data.tar.gz: efa56ac32d1591a5a47fb220f295909796e2b891bb26ab26ced879f55f0c8484
 SHA512:
-  metadata.gz: 935b6515910e2eaf6871c5cb00920cda705935d06449de61410e941dfdb185c7437a2e7fa388244997dcb338efd0221ad7cf9c9e207d0b2fa4237fd9f63166e0
-  data.tar.gz: 9d3fe3b1c638b6a72b729464a2dc5178202fe9158f88aa3d5c692498d82eda3e65760141d5233e43e7bfd083ecd68bbaf2881f97db6a828825498e1771b4bdcf
+  metadata.gz: aacdce1efe87f6d288f6167e980418def9d1f5c17c51fc255c2bdce025caf3bd80466d946b48972c5f33259a5e6aff3d38f1b529133688b0698e6e6f86b8f21c
+  data.tar.gz: db6a64d3fefd229472b6b67c96844328e7e926e9bc145602c8d72b8f40cbf2911bc7092e8401fab30dad6cdc39a09fb7e020ddc279d4c103d3425a58041db422

data/CHANGELOG.md

@@ -1,7 +1,11 @@
 # Karafka Web Changelog
 
 ## 1.0.0 (Unreleased)
-- [Fix] Add `initialize` to `Status::Context` that defines all instance variables upfront in a consistent order, giving every instance the same Ruby object shape and eliminating the `:performance` shape-variation warning.
+- [Fix] Fix two precision bugs in `Aggregators::State`/`Aggregators::Metrics` process eviction and utilization, both caught by a Copilot PR review and confirmed on the merged pipeline refactor. `evict_expired_processes` computed the ttl window via integer division (`config.ttl / 1_000`), truncating any non-multiple-of-1000 millisecond ttl and evicting processes up to ~999ms earlier than configured; it now uses float division. `RefreshCurrentStats#call` computed average utilization via `utilization / (stats[:processes] + 0.0001)`, an epsilon guard against division by zero that also systematically underestimated utilization for any nonzero process count; it now divides exactly and returns `0.0` only when there are zero active processes.
+- [Fix] Fix the real cause of the intermittent, seemingly-unrelated CI-only Pro Explorer flakes finally surfaced by the `assert_ok` diagnostic below: not a Kafka broker/timing race, but Ruby's object-shape warning (a controller class crossing 8 distinct instance-variable shapes) being turned into a hard failure by the test suite's `Warning.process` hook. Controllers, like the Roda app classes already exempted, legitimately accumulate many shapes because they conditionally set a handful of instance variables depending on the specific request branch taken (e.g. Explorer's `#show` only sets `@safe_key`/`@safe_headers`/`@safe_payload` when the message isn't a compacted/system entry). Which controller happens to cross the threshold depends on minitest's random run order, which is why it surfaced as an unrelated-looking flake instead of a stable, reproducible failure. Widened the existing `Ui::App` shape-variation exception to cover controller classes too.
+- [Enhancement] Make `assert_ok` surface the actual captured exception (class, message, backtrace) on a 500, not just the generic static error page body. Subscribes to the same `error.occurred` monitor event the production error handler already dispatches web UI errors through, capturing the last one per test. This has been the main blocker in diagnosing rare CI-only flakes in the Pro Explorer controller specs, where a failure only ever showed the generic HTML error page with no indication of what actually broke.
+- [Enhancement] Remove the OSS "support Karafka Pro" banner that was rendered on every Web UI page for non-Pro users. It's no longer needed at this stage since users are already aware of the Pro offering.
+- [Enhancement] Migrate the Web UI topic declarations to Karafka's new standalone `Karafka::App.declaratives.draw` API (Karafka `2.6.0.beta1`). The Web UI topics are declared as `active false` (Web UI manages their creation and runtime replication factor itself), replacing the deprecated routing-based `config(active: false)` bridge that was previously called on each routing topic.
 - [Enhancement] Add `Warning.process` block to the test helper to turn Ruby warnings originating from the project code into test failures.
 - [Enhancement] Enable all opt-in Ruby warning categories in the test helper via `Warning.categories` (available since Ruby 3.4), so any new categories added in future Ruby versions are automatically enabled without code changes.
 - [Enhancement] Replace sequential per-partition `query_watermark_offsets` consumer calls in `Counters#estimate_errors_count` with a single targeted `topic_info` metadata call followed by a batch `read_watermark_offsets` admin call. This eliminates the consumer connection overhead and reduces Kafka roundtrips from up to N+1 sequential calls to 3 regardless of partition count.
@@ -11,6 +15,16 @@
 - [Enhancement] Replace token-based CSRF protection (`route_csrf` plugin) with header-based protection using `Sec-Fetch-Site` header (`sec_fetch_site_csrf` plugin). This eliminates the need for CSRF tokens by leveraging browser-enforced headers that cannot be forged from cross-origin requests. Modern browsers automatically include this header, providing simpler and more robust CSRF protection.
 - [Enhancement] Include a short spec file hash in generated test topic names for traceability. Topic names now follow the `it-{hash}-{uuid}` format, making it easy to identify which test file created a given topic in Kafka logs.
 - [Change] Require Roda `>= 3.100` (previously `~> 3.69`).
+- [Fix] Harden the `wait_for_offset_visible` test helper (used after a transactional produce) to also exercise the Web UI's own message-read path, not just the admin watermark offset. The admin watermark advancing only proves the broker appended the control record; the Web UI reads with a much shorter `fetch.wait.max.ms` than the admin client and could still intermittently raise or return stale results on that exact offset (e.g. the flaky Pro Explorer `system entry` spec), even after the watermark-only wait introduced previously. The helper now also polls the same `Karafka::Web::Ui::Lib::Admin.read_topic` call the Web UI performs and requires it to complete without error before returning.
+- [Fix] Fix two more flaky Pro Explorer `#recent` specs (`when getting recent for the whole topic` / `when recent is on the first partition` and `when recent is on another partition`). Both produced a message to one partition, then a fixed `sleep(0.1)` before producing the message that should be "most recent" to another partition and immediately requesting the endpoint, racing broker propagation under CI load the same way the already-fixed single-partition `#recent` spec did. Replaced the fixed sleep with a `wait_for_message` poll on the second produce's own offset, matching the existing pattern used by the sibling spec right below it.
+- [Fix] Stop a long, unbreakable page title (e.g. a long topic name on the Pro Explorer topic page) and the breadcrumbs bar above it from overflowing the page. A grid/flex item's default `min-width: auto` let the title and breadcrumbs blow out past the viewport instead of shrinking, which pushed layout wide enough to force an unexpected page scrollbar. The title wrapper and `breadcrumbs-wrapper` now set `min-width: 0`, the title text wraps via `overflow-wrap: anywhere`, and the breadcrumbs list now wraps onto multiple lines instead of relying on an easy-to-miss horizontal scroll.
+- [Fix] Stop long, unbreakable flash messages (e.g. a long dotted/underscored topic name in a "successfully created" notice) from overflowing their alert box. DaisyUI's `.alert` grid track sized the message column to its content's intrinsic width, so long single-token strings pushed past the box edge instead of wrapping. The message `span` now sets `overflow-wrap: anywhere` and `min-width: 0` so it wraps within the alert instead.
+- [Fix] Stop long, dotted/underscored Pro Explorer, DLQ, and Topics topic-tile names from overflowing or overlapping their tile. `topic-tile-text` now sets `overflow-wrap: anywhere` so unbreakable names wrap inside the tile instead of spilling out, and the topic-tile link in those three views now carries a `title` attribute showing the full topic name on hover.
+- [Fix] Make the `create_topic` test helper wait until a freshly created topic's partitions are actually readable (expected partition count visible and watermark offsets queryable), not just until the topic name appears in cluster metadata. This removes a flaky failure in multi-partition specs (e.g. the topics distribution controller) that intermittently 404'd because watermark offsets were read before the partition leaders had propagated.
+- [Fix] Stop the array paginator from offering a "Next" link to an empty page when the last page is exactly full. `Paginators::Arrays` decided "is there a next page?" from whether the current page was full, so any list whose total size was an exact multiple of `per_page` (25/50/75/...) surfaced a Next link leading to an empty page. It now reports the last page based on whether a further slice actually exists.
+- [Fix] Compute the dashboard average batch size with float division so it is no longer floored. `Metrics::Aggregated` divided the per-window message delta by the batch delta using integer division, so e.g. 1000 messages over 47 batches charted as `21` instead of `21.28`, systematically under-reporting the average. It now uses float division rounded to 2 decimals.
+- [Fix] Include jobs in the `waiting` state when aggregating the dashboard "Pending" counter. `State#refresh_current_stats` now resets and sums `stats[:waiting]` from incoming consumer reports (previously it was never aggregated and stayed `0`), so `Counters#pending` (`enqueued + waiting`) no longer undercounts jobs sitting in advanced/recurring/scheduled-message schedulers. `:waiting` is now also validated by the `AggregatedStats` contract.
+- [Fix] Add `initialize` to `Status::Context` that defines all instance variables upfront in a consistent order, giving every instance the same Ruby object shape and eliminating the `:performance` shape-variation warning.
 - [Fix] Accept (and ignore) a block in `Karafka::Web::Producer#__getobj__` to silence Ruby 3.4's `strict_unused_block` warning emitted via `SimpleDelegator#method_missing` on every delegated producer call.
 - [Fix] Remove `cgi` as no longer needed.
 - [Fix] Exclude `test/` directory from gem releases to reduce package size.
@@ -18,6 +32,18 @@
 - [Fix] Fix alerts formatting for the distribution view.
 - [Fix] Fix 500 error in the Pro Explorer when a message payload parses as valid JSON but contains strings with invalid UTF-8 byte sequences. `JSON.pretty_generate` would raise `JSON::GeneratorError` outside of any error boundary and propagate as an unhandled 500. The pretty-print step is now wrapped in a dedicated `@safe_pretty_payload` SafeRunner; on failure the raw bytes are displayed alongside a deserialization warning.
 - [Fix] Fix 500 error in the Pro Explorer message JSON export when a payload deserializes correctly but cannot be serialized back to JSON (for example when it contains strings with invalid UTF-8 byte sequences). The export endpoint now responds with 404 in such cases and the export action button is no longer rendered for such messages.
+- [Fix] Normalize a batch of styling inconsistencies found while auditing #906: a `data-table-wraper` typo left the Cluster replication table unstyled, `Cluster::_config` rendered raw `true`/`false` instead of badges (unlike the identical `Topics::Configs` table), a Recurring Tasks "Trigger" button's disabled state was computed but never applied to its class, several views carried dead pre-Tailwind Bootstrap classes (`col-sm-*`, `col-lg-*`, `row`, `container-wrapper`) with no effect, one Topics Configs action cell was missing the `options` column class, a handful of breadcrumb/title labels had grammar or casing inconsistencies ("Cluster informations", "Consumers Groups Health", "Dead Letter Queue topics"), the OSS Routing topic list hand-rolled a `badge-warning` for inactive topics instead of the `badge_secondary` used by the identical Pro table, the filtered-payload notice used unstyled Bootstrap-era markup instead of the shared `alert_box_warning` primitive, `status-row-stopping` was colored red (`border-l-error`) while `status_badge` treats "stopping" as the same warning tier as "quiet"/"quieting", three Pro Topics checklist notices (before deleting a topic, increasing partitions, or editing a config value) hand-rolled a bare `alert` div with no severity color or icon instead of the shared `alert_box_warning` primitive used by their sibling warning boxes on the same pages, `alert_box_primary`/`alert_box_secondary` displayed the success checkmark icon (copy-pasted from `alert_box_success`) instead of matching their non-box `info_circle`/`pause_circle` siblings, the internal style-guide page demoed the wrong pencil icon for edit actions, and a scheduled message's "Cancel dispatch" button used a passive error-status icon instead of the `trash` icon already used for every other removal action.
+- [Fix] Continue normalizing styling inconsistencies from the #906 audit: Health and Recurring Tasks tab bars hand-rolled `col-span-12 mb-9` instead of the shared `tab-container-wrapper` class, and the Scheduled Messages per-partition schedule heading used `h3`/`.h3` where the equivalent per-group heading on Health pages uses `h2`/`.h2`.
+- [Fix] Retire the `.row-table`/`.row-table-wrapper` table primitive, which had drifted to a single real caller (the Pro per-topic Errors table) against 45+ real uses of `.data-table`, and additionally used a different button-alignment convention (`text-center` vs. `.data-table`'s `text-right`) than every other action column in the app. Switched that one table to `.data-table`, removed the now fully unused CSS utilities and their style-guide demo, and fixed a stale ".row-table" label left over in an unrelated `.data-table` demo section.
+- [Enhancement] Add a standardized `empty_state` helper/component (icon, message, optional description, and optional call-to-action) and replace the ad hoc `alert_info`/`alert_box_info` "There are no X" messages across every empty-list view (Jobs, DLQ, Explorer, Health, Errors, Consumers, Recurring Tasks, Scheduled Messages, dashboard, and paginated tables) with it, for a consistent look across the Web UI. Demoed on the internal style-guide `/ux` page.
+- [Fix] Fix unreadable `.btn-outline.btn-active` buttons (e.g. the dashboard time-range selector) in both the light and dark themes. The daisyUI 5.6 upgrade left the active state's background color computed from the same `--btn-color` variable as the outline's text color, so the two nearly matched; the button now switches to the color-variant's contrasting foreground color when active, matching its existing `:hover` behavior.
+- [Enhancement] Expand the internal `/ux` style-guide page to cover every UI component actually used across the app, so upgrades (daisyUI, Tailwind, etc.) can be visually spot-checked in one place: plain `.card`/`.card-body`, `.modal`/`dialog`, `.dropdown`, `.tooltip`, the `.btn-ghost`/`.btn-square`/`.btn-action`/`.btn-lockable`/`.confirm-action` button modifiers, the breadcrumbs component, and the `status_badge`/`lag_trend_badge`/`kafka_state_badge`/`lso_risk_state_badge`/`truncate`/`lag_with_label`/`offset_with_label` helper methods (previously only their raw CSS classes were demoed). Adds a small reusable `ModalOpener` JS component (`[data-modal-open]`) since the CSP disallows the inline `onclick` handler style used by the existing search modal trigger.
+- [Fix] Fix a flaky Pro Explorer spec (`when requested message exists but is a system entry`) caused by the `produce` test helper's transactional flow: it only waited a fixed `sleep(0.1)` for a transactional produce's commit control record to become visible before the test reads it back, which is too short under CI load and made the spec intermittently 404 or see stale content. Replaced the fixed sleep with a `wait_for_offset_visible` poll that waits until the control record's offset is actually part of the readable watermark range, mirroring the existing `wait_for_message`/`create_topic` readiness-polling pattern instead of a fixed delay.
+- [Fix] Stop a misclick on a Pro-gated OSS element from fully navigating away to the standalone "Pro Feature" upsell page. This affected the sidebar (Health, Explorer, Cron, Schedules, Dead, Topics), the Consumers tabs (Performance, Controls, Commands), the dashboard's "Data transfers" chart tab, and several unguarded links with no visual gating indicator at all: the dashboard's "Total lag"/"Dead" counters, Cluster topic/partition names, per-message Explorer offset links on the Errors detail page, and consumer process IDs on the Consumers and Jobs list pages. Gated sidebar/tab items are now truly inert `disabled` buttons with an "Available in Karafka Pro" hover tooltip instead of `<a href>` links (or, for the dashboard chart tab, a JS-clickable `<span>`) pointing at the real Pro-only content; the previously-unguarded inline links are now plain text in the OSS templates, with a matching Pro-only view override (`dashboard/_counters`, `cluster/_partition`, `errors/_detail`) restoring the links for Pro users, keeping the OSS templates free of any `Karafka.pro?` branching. Also fixes the sidebar's collapse/expand toggle showing the default arrow cursor instead of a pointer on hover, and hardens `TabsManager` (the chart-tab-switching JS) to no-op instead of throwing when a tab's target content or a previously-active tab is missing/disabled, which had broken tab-switching for the Utilization/RSS/Concurrency charts for anyone who had the now-disabled "Data transfers" tab persisted as their last-active tab. Closes #1106.
+- [Fix] Add `rel="noopener noreferrer"` to every `target="_blank"` link across the Web UI (docs, Slack, GitHub, and "become Pro" links in the support, status, dashboard, and Pro topic-replication warning views). Without it, the opened external page could access `window.opener` and redirect the original Web UI tab to an arbitrary page (reverse tabnabbing).
+- [Fix] Fix a flaky Pro Explorer spec (`ExplorerController#recent::when getting recent for the partition`) that produced a message and immediately requested the "recent" endpoint with no readiness wait, occasionally racing the broker's propagation of the just-produced message under CI load. Added a `wait_for_message` poll before the request, matching the existing readiness-polling pattern used elsewhere in the suite.
+- [Enhancement] Replace the bare `assert(response.ok?)` pattern with a new `assert_ok` test helper across the whole controller test suite (381 call sites). On failure it now prints the actual response status and a body excerpt instead of a generic "Expected false to be truthy", making intermittent CI-only non-200 failures actually diagnosable.
+- [Change] Switch to Karafka 2.6's new, group-type-agnostic `#group`/`group_id` accessors instead of `#consumer_group`/`consumer_group_id` when reading from Karafka's own routing and instrumentation APIs (`topic.group`, `subscription_group.group`, `event[:group_id]`), preparing for upcoming Kafka share group support (KIP-932). `consumer_group`/`consumer_group_id` remain as karafka-web's own internal naming (tracking payloads, commanding schema, UI labels) — only the calls into Karafka's own API surface changed. Closes #1022.
 
 ## 0.11.6 (2026-02-01)
 - **[Feature]** Provide ability to pause/resume all partitions of a topic at once across all consumer processes via the Health Overview page (Pro). Topic-level commands are broadcast to all processes, and each process applies the command to partitions it owns within the specified consumer group. This simplifies bulk operations compared to pausing/resuming individual partitions one by one.

data/Gemfile.lint.lock

@@ -58,11 +58,11 @@ GEM
     unicode-display_width (3.2.0)
       unicode-emoji (~> 4.1)
     unicode-emoji (4.2.0)
-    yard (0.9.38)
-    yard-lint (1.4.0)
+    yard (0.9.45)
+    yard-lint (1.10.1)
       yard (~> 0.9)
       zeitwerk (~> 2.6)
-    zeitwerk (2.7.4)
+    zeitwerk (2.8.2)
 
 PLATFORMS
   ruby
@@ -79,6 +79,7 @@ DEPENDENCIES
 
 CHECKSUMS
   ast (2.4.3) sha256=954615157c1d6a382bc27d690d973195e79db7f55e9765ac7c481c60bdb4d383
+  bundler (4.0.17) sha256=214e21431b5665dd2f99df8a5511c6b151d7a72e8015c8b38f8b775b61cbb6c1
   json (2.18.0) sha256=b10506aee4183f5cf49e0efc48073d7b75843ce3782c68dbeb763351c08fd505
   language_server-protocol (3.17.0.5) sha256=fd1e39a51a28bf3eec959379985a72e296e9f9acfce46f6a79d31ca8760803cc
   lint_roller (1.1.0) sha256=2c0c845b632a7d172cb849cc90c1bce937a28c5c8ccccb50dfd46a485003cc87
@@ -100,9 +101,9 @@ CHECKSUMS
   standard-performance (1.9.0) sha256=49483d31be448292951d80e5e67cdcb576c2502103c7b40aec6f1b6e9c88e3f2
   unicode-display_width (3.2.0) sha256=0cdd96b5681a5949cdbc2c55e7b420facae74c4aaf9a9815eee1087cb1853c42
   unicode-emoji (4.2.0) sha256=519e69150f75652e40bf736106cfbc8f0f73aa3fb6a65afe62fefa7f80b0f80f
-  yard (0.9.38) sha256=721fb82afb10532aa49860655f6cc2eaa7130889df291b052e1e6b268283010f
-  yard-lint (1.4.0) sha256=7dd88fbb08fd77cb840bea899d58812817b36d92291b5693dd0eeb3af9f91f0f
-  zeitwerk (2.7.4) sha256=2bef90f356bdafe9a6c2bd32bcd804f83a4f9b8bc27f3600fff051eb3edcec8b
+  yard (0.9.45) sha256=52e211493f7cb8a3ebf7e104a25a1e73937a3103092545d34cb88fafebb3dc51
+  yard-lint (1.10.1) sha256=172ea1905304580bd515c093d82831ec4889e725100c49d5bf77e62101f49129
+  zeitwerk (2.8.2) sha256=7212a61311083c604184b1ea2574b9aa05cd14f855a0841c06985cabe9181d12
 
 BUNDLED WITH
-  4.0.3
+  4.0.17

data/Gemfile.lock

@@ -1,10 +1,10 @@
 PATH
   remote: .
   specs:
-    karafka-web (1.0.0.beta1)
+    karafka-web (1.0.0.rc1)
       erubi (~> 1.4)
-      karafka (>= 2.5.10.rc1, < 2.7.0)
-      karafka-core (>= 2.5.0, < 2.7.0)
+      karafka (>= 2.6.0.beta1, < 2.7.0)
+      karafka-core (>= 2.6.0, < 2.7.0)
       roda (>= 3.100, < 4.0)
       tilt (~> 2.0)
 
@@ -13,8 +13,7 @@ GEM
   specs:
     byebug (13.0.0)
       reline (>= 0.6.0)
-    concurrent-ruby (1.3.6)
-    docile (1.4.1)
+    concurrent-ruby (1.3.7)
     drb (2.2.3)
     erubi (1.13.1)
     et-orbi (1.4.0)
@@ -30,17 +29,17 @@ GEM
     ffi (1.17.4-x86_64-darwin)
     ffi (1.17.4-x86_64-linux-gnu)
     ffi (1.17.4-x86_64-linux-musl)
-    fugit (1.12.2)
+    fugit (1.13.0)
       et-orbi (~> 1.4)
       raabro (~> 1.4)
     io-console (0.8.2)
-    json (2.19.7)
-    karafka (2.5.10.rc1)
-      karafka-core (>= 2.5.13, < 2.6.0)
-      karafka-rdkafka (>= 0.26.1)
-      waterdrop (>= 2.8.14, < 3.0.0)
+    json (2.20.0)
+    karafka (2.6.0.beta1)
+      karafka-core (>= 2.6.0, < 2.7.0)
+      karafka-rdkafka (>= 0.27.2)
+      waterdrop (>= 2.10.1, < 3.0.0)
       zeitwerk (~> 2.3)
-    karafka-core (2.5.13)
+    karafka-core (2.6.2)
       karafka-rdkafka (>= 0.20.0)
       logger (>= 1.6.0)
     karafka-rdkafka (0.27.2)
@@ -86,24 +85,24 @@ GEM
       prism (~> 1.5)
     mocha (3.1.0)
       ruby2_keywords (>= 0.0.5)
-    nokogiri (1.19.3)
+    nokogiri (1.19.4)
       mini_portile2 (~> 2.8.2)
       racc (~> 1.4)
-    nokogiri (1.19.3-aarch64-linux-gnu)
+    nokogiri (1.19.4-aarch64-linux-gnu)
       racc (~> 1.4)
-    nokogiri (1.19.3-aarch64-linux-musl)
+    nokogiri (1.19.4-aarch64-linux-musl)
       racc (~> 1.4)
-    nokogiri (1.19.3-arm-linux-gnu)
+    nokogiri (1.19.4-arm-linux-gnu)
       racc (~> 1.4)
-    nokogiri (1.19.3-arm-linux-musl)
+    nokogiri (1.19.4-arm-linux-musl)
       racc (~> 1.4)
-    nokogiri (1.19.3-arm64-darwin)
+    nokogiri (1.19.4-arm64-darwin)
       racc (~> 1.4)
-    nokogiri (1.19.3-x86_64-darwin)
+    nokogiri (1.19.4-x86_64-darwin)
       racc (~> 1.4)
-    nokogiri (1.19.3-x86_64-linux-gnu)
+    nokogiri (1.19.4-x86_64-linux-gnu)
       racc (~> 1.4)
-    nokogiri (1.19.3-x86_64-linux-musl)
+    nokogiri (1.19.4-x86_64-linux-musl)
       racc (~> 1.4)
     ostruct (0.6.3)
     prism (1.9.0)
@@ -118,20 +117,15 @@ GEM
     rake (13.4.2)
     reline (0.6.3)
       io-console (~> 0.5)
-    roda (3.104.0)
+    roda (3.105.0)
       rack
     ruby2_keywords (0.0.5)
-    simplecov (0.22.0)
-      docile (~> 1.1)
-      simplecov-html (~> 0.11)
-      simplecov_json_formatter (~> 0.1)
-    simplecov-html (0.13.2)
-    simplecov_json_formatter (0.1.4)
+    simplecov (1.0.2)
     tilt (2.7.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     warning (1.6.0)
-    waterdrop (2.10.1)
+    waterdrop (2.10.2)
       karafka-core (>= 2.5.12, < 3.0.0)
       karafka-rdkafka (>= 0.24.0)
       zeitwerk (~> 2.3)

data/docker-compose.yml

@@ -1,7 +1,7 @@
 services:
   kafka:
     container_name: kafka
-    image: confluentinc/cp-kafka:8.2.1
+    image: confluentinc/cp-kafka:8.3.0
 
     ports:
       - 9092:9092

data/karafka-web.gemspec

@@ -17,8 +17,8 @@ Gem::Specification.new do |spec|
   spec.licenses = %w[LGPL-3.0-only Commercial]
 
   spec.add_dependency "erubi", "~> 1.4"
-  spec.add_dependency "karafka", ">= 2.5.10.rc1", "< 2.7.0"
-  spec.add_dependency "karafka-core", ">= 2.5.0", "< 2.7.0"
+  spec.add_dependency "karafka", ">= 2.6.0.beta1", "< 2.7.0"
+  spec.add_dependency "karafka-core", ">= 2.6.0", "< 2.7.0"
   spec.add_dependency "roda", ">= 3.100", "< 4.0"
   spec.add_dependency "tilt", "~> 2.0"
 

data/lib/karafka/web/deserializer.rb

@@ -25,7 +25,7 @@ module Karafka
           # We allow duplicates keys because of a fixed bug that was causing duplicated process
           # ids to leak into the consumers states data. Once a proper migration is written, this
           # can be retired
-          # @see https://github.com/karafka/karafka-web/issues/741
+          # See https://github.com/karafka/karafka-web/issues/741
           allow_duplicate_key: true
         )
       end

data/lib/karafka/web/management/actions/create_initial_states.rb

@@ -7,8 +7,7 @@ module Karafka
         # Creates the records needed for the Web-UI to operate.
         # It creates "almost" empty states because the rest is handled via migrations
         class CreateInitialStates < Base
-          # Whole default empty state
-          # This will be further migrated by the migrator
+          # Whole default empty state. This will be further migrated by the migrator
           DEFAULT_STATE = {
             schema_version: "0.0.0"
           }.freeze

data/lib/karafka/web/management/actions/enable.rb

@@ -18,6 +18,7 @@ module Karafka
             ::Karafka::Web.config.enabled = true
 
             extend_routing
+            extend_declaratives
             setup_tracking_activity
 
             # Do not subscribe monitors or do anything else if tracking is disabled
@@ -56,7 +57,6 @@ module Karafka
               consumer_group ::Karafka::Web.config.group_id do
                 # Topic we listen on to materialize the states
                 topic ::Karafka::Web.config.topics.consumers.reports.name do
-                  config(active: false)
                   active ::Karafka::Web.config.processing.active
                   # Since we materialize state in intervals, we can poll for half of this time
                   # without impacting the reporting responsiveness
@@ -87,25 +87,21 @@ module Karafka
                 # We define those three here without consumption, so Web understands how to
                 # deserialize them when used / viewed
                 topic ::Karafka::Web.config.topics.consumers.states.name do
-                  config(active: false)
                   active false
                   deserializers(payload: payload_deserializer)
                 end
 
                 topic ::Karafka::Web.config.topics.consumers.metrics.name do
-                  config(active: false)
                   active false
                   deserializers(payload: payload_deserializer)
                 end
 
                 topic ::Karafka::Web.config.topics.consumers.commands.name do
-                  config(active: false)
                   active false
                   deserializers(payload: payload_deserializer)
                 end
 
                 topic ::Karafka::Web.config.topics.errors.name do
-                  config(active: false)
                   active false
                   deserializers(payload: payload_deserializer)
                 end
@@ -113,6 +109,33 @@ module Karafka
             end
           end
 
+          # Registers the Web UI topics in the standalone declaratives repository.
+          #
+          # They are all declared as `active false` on purpose. Web UI manages the creation and
+          # configuration of its topics on its own (via `karafka-web install` / `karafka-web
+          # migrate`), because it computes the replication factor at runtime based on the cluster
+          # size and populates the initial states right after the topics are created. Declaring
+          # them here (rather than relying on the legacy routing `config(...)` bridge) makes their
+          # existence explicit in the new declaratives subsystem while keeping them out of the
+          # generic `karafka declaratives` CLI management.
+          def extend_declaratives
+            topics = [
+              ::Karafka::Web.config.topics.errors,
+              ::Karafka::Web.config.topics.consumers.reports,
+              ::Karafka::Web.config.topics.consumers.states,
+              ::Karafka::Web.config.topics.consumers.metrics,
+              ::Karafka::Web.config.topics.consumers.commands
+            ]
+
+            ::Karafka::App.declaratives.draw do
+              topics.each do |web_topic|
+                topic web_topic.name do
+                  active false
+                end
+              end
+            end
+          end
+
           # Subscribes with all needed listeners
           def subscribe_to_monitor
             # Installs all the consumer related listeners

data/lib/karafka/web/management/actions/migrate_states_data.rb

@@ -4,8 +4,7 @@ module Karafka
   module Web
     module Management
       module Actions
-        # Command to migrate states data
-        # Useful when we have older schema and need to move forward
+        # Command to migrate states data. Useful when we have older schema and need to move forward
         class MigrateStatesData < Base
           # Runs needed migrations (if any) on the states topics
           def call

data/lib/karafka/web/management/migrations/base.rb

@@ -15,8 +15,7 @@ module Karafka
           class << self
             # First version that should **NOT** be affected by this migration
             attr_accessor :versions_until
-            # What resource does it relate it
-            # One migration should modify only one resource type
+            # What resource does it relate it. One migration should modify only one resource type
             attr_accessor :type
 
             # @param version [String] sem-ver version

data/lib/karafka/web/pro/commanding/commands/base.rb

@@ -27,6 +27,7 @@
 #
 # License: https://karafka.io/docs/Pro-License-Comm/
 # Contact: contact@karafka.io
+
 module Karafka
   module Web
     module Pro

data/lib/karafka/web/pro/commanding/commands/consumers/quiet.rb

@@ -32,7 +32,6 @@ module Karafka
   module Web
     module Pro
       module Commanding
-        # Namespace for commands the process can react to
         module Commands
           # Namespace for commands related to consumers themselves
           module Consumers

data/lib/karafka/web/pro/commanding/commands/consumers/stop.rb

@@ -32,7 +32,6 @@ module Karafka
   module Web
     module Pro
       module Commanding
-        # Namespace for commands the process can react to
         module Commands
           module Consumers
             # Sends a signal to stop the process

data/lib/karafka/web/pro/commanding/commands/consumers/trace.rb

@@ -32,7 +32,6 @@ module Karafka
   module Web
     module Pro
       module Commanding
-        # Namespace for commands the process can react to
         module Commands
           module Consumers
             # Collects all backtraces from the available Ruby threads and publishes their details

data/lib/karafka/web/pro/commanding/handlers/group_id_extractor.rb

@@ -0,0 +1,49 @@
+# frozen_string_literal: true
+
+# Karafka Pro - Source Available Commercial Software
+# Copyright (c) 2017-present Maciej Mensfeld. All rights reserved.
+#
+# This software is NOT open source. It is source-available commercial software
+# requiring a paid license for use. It is NOT covered by LGPL.
+#
+# The author retains all right, title, and interest in this software,
+# including all copyrights, patents, and other intellectual property rights.
+# No patent rights are granted under this license.
+#
+# PROHIBITED:
+# - Use without a valid commercial license
+# - Redistribution, modification, or derivative works without authorization
+# - Reverse engineering, decompilation, or disassembly of this software
+# - Use as training data for AI/ML models or inclusion in datasets
+# - Scraping, crawling, or automated collection for any purpose
+#
+# PERMITTED:
+# - Reading, referencing, and linking for personal or commercial use
+# - Runtime retrieval by AI assistants, coding agents, and RAG systems
+#   for the purpose of providing contextual help to Karafka users
+#
+# Receipt, viewing, or possession of this software does not convey or
+# imply any license or right beyond those expressly stated above.
+#
+# License: https://karafka.io/docs/Pro-License-Comm/
+# Contact: contact@karafka.io
+
+module Karafka
+  module Web
+    module Pro
+      module Commanding
+        module Handlers
+          # Module containing a helper for extracting the consumer group id out of a
+          # subscription group, shared by the commanding fetch-loop listeners
+          module GroupIdExtractor
+            # @param subscription_group [Karafka::Routing::SubscriptionGroup]
+            # @return [String] id of the consumer group the subscription group belongs to
+            def group_id_of(subscription_group)
+              subscription_group.group.id
+            end
+          end
+        end
+      end
+    end
+  end
+end

data/lib/karafka/web/pro/commanding/handlers/partitions/commands/base.rb

@@ -33,7 +33,6 @@ module Karafka
     module Pro
       module Commanding
         module Handlers
-          # Namespace for commands related to specific partitions
           module Partitions
             # Namespace for partitions related commands
             module Commands

data/lib/karafka/web/pro/commanding/handlers/partitions/listener.rb

@@ -37,6 +37,8 @@ module Karafka
             # Listener that hooks to the connection listener fetch loop flow to adjust it prior
             # to the next polling or on rebalances to execute the partition specific commands.
             class Listener
+              include Handlers::GroupIdExtractor
+
               def initialize
                 @tracker = Tracker.instance
                 @executor = Executor.new
@@ -50,7 +52,7 @@ module Karafka
                 listener = event[:caller]
                 client = event[:client]
                 subscription_group = listener.subscription_group
-                consumer_group_id = subscription_group.consumer_group.id
+                consumer_group_id = group_id_of(subscription_group)
 
                 # Get current partition assignments from the client
                 assignments = client.assignment.to_h
@@ -74,7 +76,7 @@ module Karafka
               # @param event [Karafka::Core::Monitoring::Event]
               def on_rebalance_partitions_assigned(event)
                 subscription_group = event[:subscription_group]
-                consumer_group_id = subscription_group.consumer_group.id
+                consumer_group_id = group_id_of(subscription_group)
 
                 # On rebalance, reject any pending commands for all topics and partitions
                 # that were assigned to this subscription group

data/lib/karafka/web/pro/commanding/handlers/topics/listener.rb

@@ -37,6 +37,8 @@ module Karafka
             # Listener that hooks to the connection listener fetch loop flow to adjust it prior
             # to the next polling or on rebalances to execute the topic specific commands.
             class Listener
+              include Handlers::GroupIdExtractor
+
               def initialize
                 @tracker = Tracker.instance
                 @executor = Executor.new
@@ -50,7 +52,7 @@ module Karafka
                 listener = event[:caller]
                 client = event[:client]
                 subscription_group = listener.subscription_group
-                consumer_group_id = subscription_group.consumer_group.id
+                consumer_group_id = group_id_of(subscription_group)
 
                 # Iterate over all topics in this subscription group and check for commands
                 subscription_group.topics.each do |topic|
@@ -67,7 +69,7 @@ module Karafka
               # @param event [Karafka::Core::Monitoring::Event]
               def on_rebalance_partitions_assigned(event)
                 subscription_group = event[:subscription_group]
-                consumer_group_id = subscription_group.consumer_group.id
+                consumer_group_id = group_id_of(subscription_group)
 
                 subscription_group.topics.each do |topic|
                   @tracker.each_for(consumer_group_id, topic.name) do |command|

data/lib/karafka/web/pro/commanding/listener.rb

@@ -31,10 +31,6 @@
 module Karafka
   module Web
     module Pro
-      # Namespace for things related to consumers commanding (management)
-      #
-      # This feature allows for basic of consumers. They can be stopped, moved to quiet or traced
-      # via the Web UI
       module Commanding
         # Wrapper around the Pro Iterator that yields messages with commands when needed for
         # further processing.

data/lib/karafka/web/pro/commanding/matchers/consumer_group_id.rb

@@ -48,7 +48,7 @@ module Karafka
             # @return [Boolean] true if this process has partitions assigned for the consumer group
             def matches?
               ::Karafka::App.assignments.any? do |topic, _partitions|
-                topic.consumer_group.id == consumer_group_id
+                topic.group.id == consumer_group_id
               end
             end
 

data/lib/karafka/web/pro/ui/controllers/cluster_controller.rb

@@ -32,7 +32,6 @@ module Karafka
   module Web
     module Pro
       module Ui
-        # Namespace for Pro controllers
         module Controllers
           # Cluster details controller
           class ClusterController < Web::Ui::Controllers::ClusterController

data/lib/karafka/web/pro/ui/controllers/consumers/base_controller.rb

@@ -37,6 +37,21 @@ module Karafka
           module Consumers
             # Base controller for all consumer related controllers
             class BaseController < Controllers::BaseController
+              private
+
+              # Finds the routing topic instance matching a given consumer group and topic name
+              #
+              # @param consumer_group_id [String] consumer group id to match
+              # @param topic_name [String] topic name to match
+              # @return [Karafka::Routing::Topic, nil] matching routing topic or nil if not
+              #   found (may happen when not all routing is available)
+              def find_routing_topic(consumer_group_id, topic_name)
+                Karafka::App
+                  .routes
+                  .flat_map(&:topics)
+                  .flat_map(&:to_a)
+                  .find { |r_topic| r_topic.group.id == consumer_group_id && r_topic.name == topic_name }
+              end
             end
           end
         end

data/lib/karafka/web/pro/ui/controllers/consumers/partitions/base_controller.rb

@@ -69,12 +69,7 @@ module Karafka
                   @partition_stats || raise(Karafka::Web::Errors::Ui::NotFoundError)
 
                   # Check if topic is LRJ from routing
-                  routing_topics = Karafka::App.routes.flat_map(&:topics).flat_map(&:to_a)
-
-                  @routing_topic = routing_topics.find do |r_topic|
-                    r_topic.consumer_group.id == @consumer_group_id &&
-                      r_topic.name == @topic
-                  end
+                  @routing_topic = find_routing_topic(@consumer_group_id, @topic)
 
                   # May not be found when not all routing is available. In such cases we assume
                   # that topic is not LRJ and it's up to the end user to handle this correctly.

data/lib/karafka/web/pro/ui/controllers/consumers/topics/pauses_controller.rb

@@ -146,12 +146,7 @@ module Karafka
                   @topic_stats || raise(Karafka::Web::Errors::Ui::NotFoundError)
 
                   # Check if topic is LRJ from routing
-                  routing_topics = Karafka::App.routes.flat_map(&:topics).flat_map(&:to_a)
-
-                  @routing_topic = routing_topics.find do |r_topic|
-                    r_topic.consumer_group.id == @consumer_group_id &&
-                      r_topic.name == @topic
-                  end
+                  @routing_topic = find_routing_topic(@consumer_group_id, @topic)
 
                   # May not be found when not all routing is available. In such cases we assume
                   # that topic is not LRJ and it's up to the end user to handle this correctly.

data/lib/karafka/web/pro/ui/controllers/scheduled_messages/schedules_controller.rb

@@ -33,7 +33,6 @@ module Karafka
     module Pro
       module Ui
         module Controllers
-          # Namespace for all controllers related to scheduled messages
           module ScheduledMessages
             # Controller to display list of schedules (groups) and details about each
             class SchedulesController < BaseController

data/lib/karafka/web/pro/ui/lib/patterns_detector.rb

@@ -43,7 +43,7 @@ module Karafka
           class PatternsDetector
             # Run the detection
             def call
-              detector = ::Karafka::Pro::Routing::Features::Patterns::Detector.new
+              detector = ::Karafka::Pro::Routing::Features::ConsumerGroups::Patterns::Detector.new
               topics_names = Web::Ui::Models::ClusterInfo.topics.map(&:topic_name)
 
               Karafka::App

data/lib/karafka/web/pro/ui/lib/policies/contracts/config.rb

@@ -33,7 +33,6 @@ module Karafka
     module Pro
       module Ui
         module Lib
-          # Policies related contracts
           module Policies
             # Namespace with policies related contracts
             module Contracts