karafka-web 0.10.4 → 0.11.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 13c431e0fa6d1b8927bd419298bc0ea522f0e823f91197fe989f72a9a08479ad
-  data.tar.gz: 6424f804a013bc34d1393fa79962cfacab6e6d5028726b7e90e93ada457b7a48
+  metadata.gz: 4320bd74426900e3a77f1748242c757cb44a1b0b578300a413d5a1cb706ec3de
+  data.tar.gz: 75be8a6b974829adde0b266cb2df6e1f62752a35dc271110a04a00eef93865df
 SHA512:
-  metadata.gz: e3ccb77dcf9624e1ca23473a963ea59cd8efc227feae098c7a80898b45c573eb70b564fd963abc6d3b0dd01a4b9e0577c1708bc2904afa6c5523360fc3880362
-  data.tar.gz: 60f20e2ed98fb8818164157e91ce117c5fb2d6b60f5c1371abef787f0f637269f27ed378a0ca8ffe7e95c43defddfc4749cfe1c06cbf905c8e591f8b171c2c36
+  metadata.gz: 58a4c8ed2d9d400070aa4d43bb29a73006c435c00fd4d9143dd520db01368b5984729bd947bd88a8f2c1865fff25935449150b329f9396405ec53ce82c850299
+  data.tar.gz: d1c96b677662d862d9d05a70945f3ca7fbc55359033fb7f3350600eb4e0388673bc8482f1f165f0775b5d02bf8075801e1450286b59a0fdc4bd2b2d9e5405ef7

data/CHANGELOG.md

@@ -1,5 +1,75 @@
 # Karafka Web Changelog
 
+## 0.11.2 (2025-08-18)
+- [Enhancement] Make sure that TTL counters related `#inspect` are thread-safe.
+- [Change] Add new CI action to trigger auto-doc refresh.
+- [Change] Update daisyUI to `5.0.50`
+
+## 0.11.1 (2025-06-23)
+- [Fix] Extremely high error turnover from hundreds of partitions can cause a deadlock in the reporter for transactional Web producer.
+
+## 0.11.0 (2025-06-15)
+- **[Feature]** Provide ability to pause/resume partitions on running consumers via the UI (Pro).
+- **[Feature]** Provide ability to edit offsets of running consumers (Pro).
+- **[Feature]** Support consumers that have mismatching schema in the Status page.
+- **[Feature]** Provide ability to navigate to a timestamp in the Explorer (Pro).
+- **[Feature]** Provide ability to create and delete topics from the Web UI (Pro).
+- **[Feature]** Provide ability to manage topics configuration from the Web UI (Pro).
+- **[Feature]** Provide ability to manage topics partitioning from the Web UI (Pro).
+- **[Feature]** Provide ability to inject custom CSS and JS to adjust the Web UI.
+- [Enhancement] Support KIP-82 (header values of arrays).
+- [Enhancement] Include crawl-based link validator to the CI to ensure no dead links are generated.
+- [Enhancement] Allow for custom links in the navigation (Pro).
+- [Enhancement] Optimize topic specific lookups (Pro).
+- [Enhancement] Replace simple in-process metadata cache with user tracking version for multi-process deployments improvements.
+- [Enhancement] Move web ui topics configuration into config.
+- [Enhancement] Upgrade DaisyUI to 5.0 and Tailwind to 4.0.
+- [Enhancement] Make consumer sampler/stats gathering compatible across debian/alpine/wolfi OSes (chen-anders)
+- [Enhancement] Promote consumers lags statistics chart to OSS.
+- [Enhancement] Promote consumers RSS statistics chart to OSS.
+- [Enhancement] Remove state cache usage that complicated ability to manage topics.
+- [Enhancement] Improve flash messages.
+- [Enhancement] Improve handling of post-submit redirects.
+- [Enhancement] Provide better support for fully transactional consumers.
+- [Enhancement] Error out when `#setup` is called after `#enable!`.
+- [Enhancement] Use more performant Kafka API calls to describe topics.
+- [Enhancement] Inject `.action-NAME` and `.controller-NAME` body classes for usage with custom CSS and JS.
+- [Enhancement] Improve error handling in the commanding iterator listener (Pro).
+- [Enhancement] Introduce `trace_id` to the errors tracked for DLQ correlation (if in use) (Pro).
+- [Enhancement] Normalize how topics with partitions data is being displayed (`topic-[0,1,2]` etc).
+- [Change] Do not fully hide config-disabled features but make them disabled.
+- [Change] Remove per-consumer process duplicated details from Subscriptions and Jobs tabs.
+- [Change] Move to trusted-publishers and remove signing since no longer needed.
+- [Refactor] Make sure all temporary topics have a `it-` prefix in their name.
+- [Refactor] Introduce a `bin/verify_topics_naming` script to ensure proper test topics naming convention.
+- [Fix] Closest time based lookup redirect fails.
+- [Fix] Fi incorrect error type in commanding listener from `web.controlling.controller.error` to `web.commanding.listener.error` (Pro).
+- [Fix] Topic named messages collides with the explorer routes.
+- [Fix] Fix a case where live poll button enabling would not immediately start refreshes.
+- [Fix] Fix negative message deserialization allocation stats.
+- [Fix] Fix incorrect background color in some of the alert notices.
+- [Fix] Support dark mode in error pages.
+- [Fix] Fix incorrect names in some of the tables headers.
+- [Fix] Normalize position of commanding buttons in regards to other UI elements.
+- [Fix] Fix incorrect indentation of some of the info messages.
+- [Fix] Fix tables headers inconsistent alignments.
+- [Fix] Fix incorrect warning box header color in the dark mode.
+- [Fix] Fix missing breadcrumbs on the consumers overview page.
+- [Fix] Fix a case where disabled buttons would be enabled back too early.
+- [Fix] The recent page breadcrumbs and offset id are not refreshed on change.
+- [Fix] Direct URL access with too big partition causes librdkafka crash.
+- [Fix] Fix incorrect breadcrumbs for pending consumer jobs.
+- [Fix] Allow for using default search matchers in Karafka Web UI topics including Errors.
+- [Fix] Ensure that when flashes or alerts are visible, pages are not auto-refreshed (would cause them to dissapear).
+- [Fix] Time selector in the explorer does not disappear after clicking out.
+- [Fix] Tombstone message presentation epoch doesn't make sense.
+- [Fix] Fix incorrectly displayed "No jobs" alert info.
+- [Fix] Previous / next navigation in the explorer does not work when moving to transactional checkpoints.
+- [Fix] Errors explorer does not work with transactional produced data.
+- [Fix] Errors explorer in OSS does not have pagination.
+- [Maintenance] Require `karafka-core` `>= 2.4.8` and `karafka` `>= 2.4.16`.
+- [Maintenance] Update `AirDatepicker` to `3.6.0`.
+
 ## 0.10.4 (2024-11-26)
 - **[Breaking]** Drop Ruby `3.0` support according to the EOL schedule.
 - [Enhancement] Extract producers tracking `sync_threshold` into an internal config.
@@ -88,39 +158,6 @@
 - [Fix] License identifier `LGPL-3.0` is deprecated for SPDX (#2177).
 - [Fix] Do not include prettifying the payload for visibility in the resource computation cost.
 
-### Upgrade Notes
-
-This is a **major** release that brings many things to the table.
-
-This version of the Karafka Web UI requires Karafka `>= 2.4.7`. You can either upgrade both or upgrade Karafka first and then the Web UI. Karafka `2.4.7` is also compatible with Web UI `0.9.1`; thus, you can upgrade one at a time.
-
-#### Configuration
-
-Visibility Filters have been reorganized into messages policies.
-
-Please read the [Policies API](https://karafka.io/docs/Pro-Web-UI-Policies/) documentation and convert your visibility filters to policies.
-
-Your existing message-related visibility filter policies should now be assigned to a new configuration:
-
-```ruby
-Karafka::Web.setup do |config|
-  config.ui.policies.messages = MyCustomRequestsPolicy.new
-end
-```
-
-#### Deployment
-
-Because of the reporting schema update, it is recommended to:
-
-0. Make sure you have upgraded to `0.9.1` before and that it was fully deployed.
-1. Test the upgrade on a staging or dev environment.
-3. The Web UI interface may throw 500 errors during the upgrade because of schema incompatibility (until Puma is deployed and all consumers redeployed). This will have no long-term effects and can be ignored.
-4. `Karafka::Web::Errors::Processing::IncompatibleSchemaError` **is expected**. It is part of the Karafka Web UI zero-downtime deployment strategy. This error allows the Web UI materialization consumer to back off and wait for it to be replaced with a new one.
-5. Perform a rolling deployment (or a regular one) and replace all consumer processes.
-6. Update the Web UI Puma.
-7. **No** CLI command execution is required.
-8. Enjoy.
-
 ## 0.9.1 (2024-05-03)
 - [Fix] OSS `lag_stored` for not-subscribed consumers causes Web UI to crash.
 
@@ -158,12 +195,6 @@ Because of the reporting schema update, it is recommended to:
 - [Fix] Fix dangling `console.log`.
 - [Fix] Fix a case where consumer assignments would not be truncated on the consumers view.
 
-### Upgrade Notes
-
-This is a **major** release that brings many things to the table.
-
-This version of the Karafka Web UI should be upgraded together with Karafka. All upgrade documentation for Karafka and Web UI `0.9` can be found [here](https://karafka.io/docs/Upgrades-2.4/).
-
 ## 0.8.2 (2024-02-16)
 - [Enhancement] Defer scheduler background thread creation until needed allowing for forks.
 - [Enhancement] Tag forks with fork indication + ppid reference when operating in swarm.
@@ -212,28 +243,6 @@ This version of the Karafka Web UI should be upgraded together with Karafka. All
 - [Change] Rename "Active subscriptions" to "Subscriptions" as process subscriptions are always active.
 - [Maintenance] Introduce granular subscription group contracts.
 
-### Upgrade Notes
-
-This is a **major** release that brings many things to the table.
-
-#### Configuration
-
-**No** configuration changes are needed.
-
-#### Deployment
-
-Because of the reporting schema update, it is recommended to:
-
-0. Make sure you have upgraded to `0.7.10` before and that it was fully deployed.
-1. Test the upgrade on a staging or dev environment.
-2. Starting from `0.7.0` Karafka Web UI supports rolling deploys, so there is no need to "stop the world".
-3. The Web UI interface may throw 500 errors during the upgrade because of schema incompatibility (until Puma is deployed). This will have no long-term effects and can be ignored.
-4. `Karafka::Web::Errors::Processing::IncompatibleSchemaError` **is expected**. It is part of the Karafka Web UI zero-downtime deployment strategy. This error allows the Web UI materialization consumer to back off and wait for it to be replaced with a new one.
-5. Perform a rolling deployment (or a regular one) and replace all consumer processes.
-6. Update the Web UI Puma.
-7. **No** CLI command execution is required. Starting from this release (`0.8.0`), the Karafka Web UI contains an automatic schema migrator that allows it to automatically adjust internal topic data formats.
-8. Enjoy.
-
 ## 0.7.10 (2023-10-31)
 - [Fix] Max LSO chart does not work as expected (#201)
 
@@ -265,14 +274,6 @@ Because of the reporting schema update, it is recommended to:
 - [Maintenance] Include license and copyrights notice for `timeago.js` that was missing in the JS min file. 
 - [Refactor] Rename `ui.show_internal_topics` to `ui.visibility.internal_topics_display`
 
-### Upgrade Notes
-
-**NO** rolling upgrade needed. Just configuration update.
-
-1. If you are using `ui.visibility_filter` this option is now `ui.visibility.filter` (yes, only `.` difference).
-2. If you are using a custom visibility filter, it requires now two extra methods: `#download?` and `#export?`. The default visibility filter allows both actions unless message is encrypted.
-3. `ui.show_internal_topics` config option has been moved and renamed to `ui.visibility.internal_topics`.
-
 ## 0.7.4 (2023-09-19)
 - [Improvement] Skip aggregations on older schemas during upgrades. This only skips process-reports (that are going to be rolled) on the 5s window in case of an upgrade that should not be a rolling one anyhow. This simplifies the operations and minimizes the risk on breaking upgrades.
 - [Fix] Fix not working `ps` for macOS.
@@ -367,48 +368,6 @@ Because of the reporting schema update, it is recommended to:
 - [Refactor] Use Roda `custom_block_results` plugin for controllers results handling.
 - [Maintenance] Require `karafka` `2.2.0` due to fixes in the Iterator API and routing API extensions.
 
-### Upgrade Notes
-
-This is a **major** release that brings many things to the table.
-
-#### Configuration
-
-Karafka Web UI now relies on Roda session management. Please configure the `ui.sessions.secret` key with a secret value string of at least 64 characters:
-
-```ruby
-# Configure it BEFORE enabling
-Karafka::Web.setup do |config|
-  # REPLACE THIS with your own value. You can use `SecureRandom.hex(64)` to generate it
-  # You may want to set it per ENV
-  config.ui.sessions.secret = 'REPLACE ME! b94b2215cc66371f2c34b7d0c0df1a010f83ca45 REPLACE ME!'
-end
-
-Karafka::Web.enable!
-```
-
-#### Deployment
-
-Because of the reporting schema update and new web-ui topics introduction, it is recommended to:
-
-0. Make sure you have upgraded to `0.6.3` before and that it was deployed. To all the environments you want to migrate to `0.7.0`.
-1. Upgrade the codebase based on the below details.
-2. **Stop** the consumer materializing Web-UI. Unless you are running a Web-UI dedicated consumer as recommended [here](https://karafka.io/docs/Web-UI-Development-vs-Production/), you will have to stop all the consumers. This is **crucial** because of schema changes. `karafka-web` `0.7.0` introduces the detection of schema changes, so this step should not be needed in the future.
-3. Run a migration command: `bundle exec karafka-web migrate` that will create missing states and missing topics. You **need** to run it for each of the environments where you use Karafka Web UI.
-4. Deploy **all** the Karafka consumer processes (`karafka server`).
-5. Deploy the Web update to your web server and check that everything is OK by visiting the status page.
-
-Please note that if you decide to use the updated Web UI with not updated consumers, you may hit a 500 error, or offset-related data may not be displayed correctly.
-
-#### Code and API changes
-
-1. `bundle exec karafka-web install` is now a single-purpose command that should run **only** when installing the Web-UI for the first time.
-2. For creating needed topics and states per environment and during upgrades, please use the newly introduced non-destructive `bundle exec karafka-web migrate`. It will assess changes required and will apply only those.
-3. Is no longer`ui.decrypt` has been replaced with `ui.visibility_filter` API. This API by default also does not decrypt data. To change this behavior, please implement your visibility filter as presented in our documentation.
-4. Karafka Web UI `0.7.0` introduces an in-memory topics cache for some views. This means that rapid topics changes (repartitions/new topics) may be visible up to 5 minutes after those changes.
-3. `ui.decrypt` setting has been replaced with `ui.visibility_filter` API. This API by default also does not decrypt data. To change this behavior, please implement your visibility filter as presented in our documentation.
-4. Karafka Web-UI `0.7.0` introduces an in-memory topics cache for some views. This means that rapid topics changes (repartitions/new topics) may be visible up to 5 minutes after those changes.
-5. Karafka Web UI requires now a new topic called `karafka_consumers_metrics`. If you use strict topic creation and ACL policies, please make sure it exists and that Karafka can both read and write to it.
-
 ## 0.6.3 (2023-07-22)
 - [Fix] Remove files from 0.7.0 accidentally added to the release.
 
@@ -446,38 +405,6 @@ Please note that if you decide to use the updated Web UI with not updated consum
 - [Refactor] Remove not used and redundant partials.
 - [Maintenance] Require `karafka` `2.1.4` due to fixes in metrics usage for workless flows.
 
-### Upgrade Notes
-
-Because of the reporting schema update, it is recommended to:
-
-- First, deploy **all** the Karafka consumer processes (`karafka server`)
-- Deploy the Web update to your web server.
-
-Please note that if you decide to use the updated Web UI with not updated consumers, you may hit a 500 error or offset related data may not be displayed correctly.
-
-#### Disabling producers instrumentation
-
-Producers error tracking **is** enabled by default. If you want to opt out of it, you need to disable the producers' instrumentation by clearing the producers' listeners:
-
-```ruby
-Karafka::Web.setup do |config|
-  # Do not instrument producers with web-ui listeners
-  config.tracking.producers.listeners = []
-end
-```
-
-#### Custom producers instrumentation
-
-By default, Karafka Web-UI instruments only `Karafka.producer`. If you use producers initialized by yourself, you need to connect the listeners to them manually. To do so, run the following code:
-
-```ruby
-::Karafka::Web.config.tracking.producers.listeners.each do |listener|
-  MY_CUSTOM_PRODUCER.monitor.subscribe(listener)
-end
-```
-
-Please make sure **not** to do it for the default `Karafka.producer` because it is instrumented out of the box.
-
 ## 0.5.2 (2023-05-22)
 - [Improvement] Label ActiveJob consumers jobs with `active_job` tag.
 - [Improvement] Label Virtual Partitions consumers with `virtual` tag.
@@ -494,15 +421,6 @@ Please make sure **not** to do it for the default `Karafka.producer` because it
 - [Fix] Fix misspelling of word `committed`.
 - [Fix] Shutdown and revocation jobs statistics extraction crashes when idle initialized without messages (#53)
 
-### Upgrade Notes
-
-Because of the reporting schema change, it is recommended to:
-
-- First, deploy **all** the Karafka consumer processes (`karafka server`)
-- Deploy the Web update to your web server.
-
-Please note that if you decide to use the updated Web UI with not updated consumers, you may hit a 500 error or offset related data may not be displayed correctly.
-
 ## 0.4.1 (2023-04-12)
 - [Improvement] Replace the "x time ago" in the code explorer with an exact date (`2023-04-12 10:16:48.596 +0200 `).
 - [Improvement] When hovering over a message timestamp, a label with raw numeric timestamp will be presented.
@@ -515,26 +433,11 @@ Please note that if you decide to use the updated Web UI with not updated consum
 - [Fix] Add missing support for using multiple subscription groups within a single consumer group.
 - [Fix] Mask SASL credentials in topic routing view (#46)
 
-### Upgrade Notes
-
-Because of the reporting schema change, it is recommended to:
-
-- First, deploy **all** the Karafka consumer processes (`karafka server`)
-- Deploy the Web update to your web server.
-
-Please note that if you decide to use the updated Web UI with not updated consumers, you may hit a 500 error.
-
 ## 0.3.1 (2023-03-27)
 - [Fix] Add missing retention policy for states topic.
 - [Fix] Fix display of compacted messages placeholders for offsets lower than low watermark.
 - [Fix] Fix invalid pagination per page count.
 
-### Upgrade Notes
-
-If upgrading from `0.3.0`, nothing.
-
-If upgrading from lower, please follow `0.3.0` upgrade procedure.
-
 ## 0.3.0 (2023-03-27)
 - **[Feature]** Support paginating over compacted topics partitions.
 - [Improvement] Display watermark offsets in the errors view.
@@ -554,15 +457,6 @@ If upgrading from lower, please follow `0.3.0` upgrade procedure.
 - [Maintenance] Remove compatibility fallbacks for job and process tags (#1342)
 - [Maintenance] Extract base sampler for tracking and web.
 
-### Upgrade Notes
-
-Because of the removal of compatibility fallbacks for some metrics fetches, it is recommended to:
-
-- First, deploy **all** the Karafka consumer processes (`karafka server`)
-- Deploy the Web update to your web server.
-
-Please note that if you decide to use the updated Web UI with not updated consumers, you may hit a 500 error.
-
 ## 0.2.5 (2023-03-17)
 - [Fix] Critical instrumentation async errors intercepted by Web don't have JID for job removal (#1366)
 

data/Gemfile

@@ -10,6 +10,8 @@ group :test do
   gem 'byebug'
   gem 'factory_bot'
   gem 'fugit'
+  # Needed for links extraction for visits verification
+  gem 'nokogiri'
   gem 'ostruct'
   gem 'rack-test'
   gem 'rspec'

data/Gemfile.lock

@@ -1,18 +1,19 @@
 PATH
   remote: .
   specs:
-    karafka-web (0.10.4)
+    karafka-web (0.11.2)
       erubi (~> 1.4)
-      karafka (>= 2.4.10, < 2.5.0)
-      karafka-core (>= 2.4.0, < 2.5.0)
+      karafka (>= 2.5.0.rc2, < 2.6.0)
+      karafka-core (>= 2.5.0, < 2.6.0)
       roda (~> 3.68, >= 3.69)
       tilt (~> 2.0)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.2.1)
+    activesupport (7.2.2.2)
       base64
+      benchmark (>= 0.3)
       bigdecimal
       concurrent-ruby (~> 1.0, >= 1.3.1)
       connection_pool (>= 2.2.5)
@@ -23,89 +24,121 @@ GEM
       securerandom (>= 0.3)
       tzinfo (~> 2.0, >= 2.0.5)
     base64 (0.2.0)
-    bigdecimal (3.1.8)
-    byebug (11.1.3)
-    concurrent-ruby (1.3.4)
-    connection_pool (2.4.1)
-    diff-lcs (1.5.1)
-    docile (1.4.0)
-    drb (2.2.1)
-    erubi (1.13.0)
+    benchmark (0.4.1)
+    bigdecimal (3.1.9)
+    byebug (12.0.0)
+    concurrent-ruby (1.3.5)
+    connection_pool (2.5.3)
+    diff-lcs (1.6.2)
+    docile (1.4.1)
+    drb (2.2.3)
+    erubi (1.13.1)
     et-orbi (1.2.11)
       tzinfo
-    factory_bot (6.5.0)
-      activesupport (>= 5.0.0)
-    ffi (1.17.0)
+    factory_bot (6.5.5)
+      activesupport (>= 6.1.0)
+    ffi (1.17.2)
     fugit (1.11.1)
       et-orbi (~> 1, >= 1.2.11)
       raabro (~> 1.4)
-    i18n (1.14.5)
+    i18n (1.14.7)
       concurrent-ruby (~> 1.0)
-    karafka (2.4.10)
+    karafka (2.5.0)
       base64 (~> 0.2)
-      karafka-core (>= 2.4.3, < 2.5.0)
-      karafka-rdkafka (>= 0.17.2)
-      waterdrop (>= 2.7.3, < 3.0.0)
+      karafka-core (>= 2.5.2, < 2.6.0)
+      karafka-rdkafka (>= 0.19.5)
+      waterdrop (>= 2.8.3, < 3.0.0)
       zeitwerk (~> 2.3)
-    karafka-core (2.4.4)
-      karafka-rdkafka (>= 0.15.0, < 0.18.0)
-    karafka-rdkafka (0.17.3)
+    karafka-core (2.5.2)
+      karafka-rdkafka (>= 0.19.2, < 0.21.0)
+      logger (>= 1.6.0)
+    karafka-rdkafka (0.19.5)
       ffi (~> 1.15)
       mini_portile2 (~> 2.6)
       rake (> 12)
-    logger (1.6.1)
-    mini_portile2 (2.8.7)
-    minitest (5.25.1)
-    ostruct (0.6.1)
+    logger (1.7.0)
+    mini_portile2 (2.8.9)
+    minitest (5.25.5)
+    nokogiri (1.18.9)
+      mini_portile2 (~> 2.8.2)
+      racc (~> 1.4)
+    nokogiri (1.18.9-aarch64-linux-gnu)
+      racc (~> 1.4)
+    nokogiri (1.18.9-aarch64-linux-musl)
+      racc (~> 1.4)
+    nokogiri (1.18.9-arm-linux-gnu)
+      racc (~> 1.4)
+    nokogiri (1.18.9-arm-linux-musl)
+      racc (~> 1.4)
+    nokogiri (1.18.9-arm64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.18.9-x86_64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.18.9-x86_64-linux-gnu)
+      racc (~> 1.4)
+    nokogiri (1.18.9-x86_64-linux-musl)
+      racc (~> 1.4)
+    ostruct (0.6.3)
     raabro (1.4.0)
-    rack (3.1.4)
-    rack-test (2.1.0)
+    racc (1.8.1)
+    rack (3.1.16)
+    rack-test (2.2.0)
       rack (>= 1.3)
     rackup (0.2.3)
       rack (>= 3.0.0.beta1)
       webrick
     rake (13.2.1)
-    roda (3.81.0)
+    roda (3.92.0)
       rack
-    rspec (3.13.0)
+    rspec (3.13.1)
       rspec-core (~> 3.13.0)
       rspec-expectations (~> 3.13.0)
       rspec-mocks (~> 3.13.0)
-    rspec-core (3.13.0)
+    rspec-core (3.13.4)
       rspec-support (~> 3.13.0)
-    rspec-expectations (3.13.1)
+    rspec-expectations (3.13.5)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-mocks (3.13.1)
+    rspec-mocks (3.13.5)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-support (3.13.1)
-    securerandom (0.3.1)
+    rspec-support (3.13.4)
+    securerandom (0.4.1)
     simplecov (0.22.0)
       docile (~> 1.1)
       simplecov-html (~> 0.11)
       simplecov_json_formatter (~> 0.1)
-    simplecov-html (0.12.3)
+    simplecov-html (0.13.1)
     simplecov_json_formatter (0.1.4)
-    tilt (2.4.0)
+    tilt (2.6.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
-    waterdrop (2.7.4)
-      karafka-core (>= 2.4.3, < 3.0.0)
-      karafka-rdkafka (>= 0.15.1)
+    waterdrop (2.8.4)
+      karafka-core (>= 2.4.9, < 3.0.0)
+      karafka-rdkafka (>= 0.19.2)
       zeitwerk (~> 2.3)
-    webrick (1.8.1)
-    zeitwerk (2.6.17)
+    webrick (1.9.1)
+    zeitwerk (2.6.18)
 
 PLATFORMS
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  arm-linux-gnu
+  arm-linux-musl
+  arm64-darwin
   ruby
-  x86_64-linux
+  x86-linux-gnu
+  x86-linux-musl
+  x86_64-darwin
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
   byebug
   factory_bot
   fugit
   karafka-web!
+  nokogiri
   ostruct
   rack-test
   rackup (~> 0.2)
@@ -113,4 +146,4 @@ DEPENDENCIES
   simplecov
 
 BUNDLED WITH
-   2.5.14
+   2.6.9

data/LICENSE

@@ -6,8 +6,12 @@ for license text.
 
 Karafka and Karafka Web have also commercial-friendly license, commercial support and commercial components.
 
-All of the commercial components are present in the lib/karafka/pro and lib/karafka/web/pro
-directory of this repository and their usage requires commercial license agreement.
+All of the commercial components and code are present in the:
+
+- `lib/karafka/web/pro`
+- `spec/lib/karafka/web/pro`
+
+directories of this repository and their usage requires commercial license agreement.
 
 By sending a pull request to the pro components, you are agreeing to transfer the copyright of your
 code to Maciej Mensfeld.

data/Rakefile

@@ -0,0 +1,4 @@
+# frozen_string_literal: true
+
+require 'bundler/setup'
+require 'bundler/gem_tasks'

data/bin/verify_kafka_warnings

@@ -0,0 +1,35 @@
+#!/bin/bash
+
+# Checks Kafka logs for unsupported warning patterns
+# Only specified warnings are allowed, all others should trigger failure
+
+allowed_patterns=(
+   "Performing controller activation"
+   "registered with feature metadata.version"
+   "Replayed TopicRecord for"
+   "Replayed PartitionRecord for"
+   "Previous leader None and previous leader epoch"
+   "Creating new"
+)
+
+# Get all warnings
+warnings=$(docker logs --since=0 kafka | grep WARN)
+exit_code=0
+
+while IFS= read -r line; do
+   allowed=0
+   for pattern in "${allowed_patterns[@]}"; do
+       if echo "$line" | grep -q "$pattern"; then
+           allowed=1
+           break
+       fi
+   done
+
+   if [ $allowed -eq 0 ]; then
+       echo "Unexpected warning found:"
+       echo "$line"
+       exit_code=1
+   fi
+done <<< "$warnings"
+
+exit $exit_code

data/bin/verify_topics_naming

@@ -0,0 +1,35 @@
+#!/usr/bin/env ruby
+
+# This script verifies that we do not create (except few needed exceptions) test topics that do
+# not start with the "it-" prefix which is our standard.
+#
+# This ensures that we can clearly identify all test topics for removal in case of doing dev work
+# on a long-lived Kafka cluster without option to fully reset it.
+#
+# It also ensures we have one convention that we can follow.
+
+require 'bundler'
+Bundler.setup(:default, :test, :integrations)
+require 'karafka'
+
+module Karafka
+  class App
+    setup do |config|
+      config.kafka = { 'bootstrap.servers': '127.0.0.1:9092' }
+    end
+  end
+end
+
+# Please note that "__" starting topics are not here by default. It is expected.
+invalid = Karafka::Admin
+          .cluster_info
+          .topics
+          .map { |topic| topic[:topic_name] }
+          .select { |topic| !topic.start_with?('it-') }
+          .select { |topic| topic.length <= 6 }
+
+invalid.each do |invalid_name|
+  puts "#{invalid_name} does not start with the \"it-\" prefix"
+end
+
+exit invalid.empty? ? 0 : 1

data/config/locales/pro_errors.yml

@@ -22,6 +22,7 @@ en:
       ui.branding.type_format: 'must be :info, :error, :warning, :success, :primary or :secondary'
       ui.branding.label_format: must be false or non-empty string
       ui.branding.notice_format: must be false or non-empty string
+      ui.branding.nav_extras_format: must be an ERB template code or a path to one
 
     search_form:
       missing: needs to be present

data/config/locales/slogans.yml

@@ -43,7 +43,7 @@ en:
     - "Are you concerned about managing large data flows? Virtual Partitions in Karafka Pro simplify data processing, offering unparalleled efficiency and scalability."
     - "Looking for flexible scheduling solutions? Karafka's Pro Periodic Jobs feature allows precise task timing and execution, enhancing your application's performance and reliability."
     - "Need advanced routing capabilities? Routing Patterns in Karafka Pro provide dynamic message routing, improving your system's adaptability and efficiency."
-    - "Are you Seeking to control your workload? With Rate Limiting in Karafka Pro, you can effectively manage and balance your system's load, ensuring optimal performance under any conditions."
+    - "Are you seeking to control your workload? With Rate Limiting in Karafka Pro, you can effectively manage and balance your system's load, ensuring optimal performance under any conditions."
     - "Need quick data access methods? The Iterator API in Karafka Pro provides efficient data retrieval methods."
     - "Want more nuanced error handling? Discover Granular Backoffs in Karafka Pro, which allows for detailed control over retry mechanisms and error recovery processes."
     - "Need a boost in data processing speed? Multiplexing in Karafka Pro enables parallel processing, significantly increasing throughput and reducing processing times."

data/docker-compose.yml

@@ -3,7 +3,7 @@ version: '2'
 services:
   kafka:
     container_name: kafka
-    image: confluentinc/cp-kafka:7.7.1
+    image: confluentinc/cp-kafka:8.0.0
 
     ports:
       - 9092:9092

data/gulpfile.js

@@ -3,7 +3,6 @@ const concat = require('gulp-concat');
 const uglify = require('gulp-uglify');
 const through2 = require('through2');
 const path = require('path');
-const cleanCSS = require('gulp-clean-css');
 const sourcemaps = require('gulp-sourcemaps');
 
 // Check if we are in development mode
@@ -64,7 +63,6 @@ gulp.task('styles', function() {
   return gulp.src(cssFiles)
     .pipe(isDev ? sourcemaps.init() : through2.obj()) // Initialize sourcemaps in dev
     .pipe(concat('application.min.css'))
-    .pipe(cleanCSS({ level: 2 })) // Minify CSS
     .pipe(isDev ? sourcemaps.write('.') : through2.obj()) // Write sourcemaps in dev
     .pipe(gulp.dest('lib/karafka/web/ui/public/stylesheets'));
 });