karafka 2.5.2 → 2.5.4.rc1

data/.github/workflows/push.yml

@@ -1,35 +0,0 @@
-name: Push Gem
-
-on:
-  push:
-    tags:
-      - v*
-
-permissions:
-  contents: read
-
-jobs:
-  push:
-    if: github.repository_owner == 'karafka'
-    runs-on: ubuntu-latest
-    environment: deployment
-
-    permissions:
-      contents: write
-      id-token: write
-
-    steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
-        with:
-          fetch-depth: 0
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@d5126b9b3579e429dd52e51e68624dda2e05be25 # v1.267.0
-        with:
-          bundler-cache: false
-
-      - name: Bundle install
-        run: |
-          bundle install --jobs 4 --retry 3
-
-      - uses: rubygems/release-gem@1c162a739e8b4cb21a676e97b087e8268d8fc40b # v1.1.2

data/.github/workflows/trigger-wiki-refresh.yml

@@ -1,30 +0,0 @@
-name: Trigger Wiki Refresh
-
-on:
-  release:
-    types: [published]
-  push:
-    branches: [master]
-
-jobs:
-  trigger-wiki-refresh:
-    runs-on: ubuntu-latest
-    environment: wiki-trigger
-    if: github.repository_owner == 'karafka'
-    steps:
-      - name: Trigger wiki refresh
-        uses: peter-evans/repository-dispatch@5fc4efd1a4797ddb68ffd0714a238564e4cc0e6f # v4.0.0
-        with:
-          token: ${{ secrets.WIKI_REPO_TOKEN }}
-          repository: karafka/wiki
-          event-type: sync-trigger
-          client-payload: |
-            {
-              "repository": "${{ github.repository }}",
-              "event_name": "${{ github.event_name }}",
-              "release_tag": "${{ github.event.release.tag_name || '' }}",
-              "release_name": "${{ github.event.release.name || '' }}",
-              "commit_sha": "${{ github.sha }}",
-              "commit_message": "Trigger Wiki Refresh",
-              "triggered_by": "${{ github.actor }}"
-            }

data/.github/workflows/verify-action-pins.yml

@@ -1,16 +0,0 @@
-name: Verify Action Pins
-on:
-  pull_request:
-    paths:
-      - '.github/workflows/**'
-jobs:
-  verify_action_pins:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
-      - name: Check SHA pins
-        run: |
-          if grep -E -r "uses: .*/.*@(v[0-9]+|main|master)($|[[:space:]]|$)" --include="*.yml" --include="*.yaml" .github/workflows/ | grep -v "#"; then
-            echo "::error::Actions should use SHA pins, not tags or branch names"
-            exit 1
-          fi

data/.gitignore

@@ -1,69 +0,0 @@
-# bundler state
-/.bundle
-/vendor/bundle/
-/vendor/ruby/
-/ruby/
-app.god
-
-# minimal Rails specific artifacts
-/.coditsu/local.yml
-db/*.sqlite3
-/log/development.log
-/log/production.log
-/log/test.log
-/tmp/*
-*.gem
-*.~
-
-# various artifacts
-**.war
-*.rbc
-*.sassc
-.byebug_history
-.redcar/
-.capistrano/
-.sass-cache
-/config/god/sidekiq.rb
-/config/puma.rb
-/coverage.data
-/coverage/
-/doc/api/
-/doc/app/
-/doc/yard
-/doc/features.html
-/doc/specs.html
-/spec/tmp/*
-/cache
-/capybara*
-/capybara-*.html
-/gems
-/specifications
-rerun.txt
-pickle-email-*.html
-
-# If you find yourself ignoring temporary files generated by your text editor
-# or operating system, you probably want to add a global ignore instead:
-#   git config --global core.excludesfile ~/.gitignore_global
-#
-# Here are some files you may want to ignore globally:
-
-# scm revert files
-**.orig
-
-# Mac finder artifacts
-.DS_Store
-
-# Netbeans project directory
-/nbproject
-
-# RubyMine project files
-.idea
-
-# Textmate project files
-/*.tmproj
-
-# vim artifacts
-**.swp
-
-# documentation
-.yardoc

data/.rspec

@@ -1,7 +0,0 @@
---require spec_helper
-# Integration specs run with their one framework, not via RSpec
---exclude-pattern "spec/integrations/**/*_spec.rb"
-# Do not run pro at the same time as default specs as it would cause state conflicts
---tag ~type:pro
-# Do not run fork because they need to run in isolation
---tag ~mode:fork

data/.ruby-gemset

@@ -1 +0,0 @@
-karafka

data/.ruby-version

@@ -1 +0,0 @@
-3.4.7

data/CODE_OF_CONDUCT.md

@@ -1,46 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at maciej@mensfeld.pl. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -1,32 +0,0 @@
-# Contributing
-
-## Introduction
-
-First, thank you for considering contributing to the Karafka ecosystem! It's people like you that make the open source community such a great community! 😊
-
-We welcome any type of contribution, not only code. You can help with:
-- **QA**: file bug reports, the more details you can give the better (e.g. screenshots with the console open)
-- **Marketing**: writing blog posts, howto's, printing stickers, ...
-- **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ...
-- **Code**: take a look at the [open issues](https://github.com/karafka/karafka/issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them.
-
-## Submitting code
-
-Any code change should be submitted as a pull request. The description should explain what the code does and give steps to execute it. The pull request should also contain tests.
-
-### Code review process
-
-Each pull request must pass all the rspec specs and meet our quality requirements.
-
-To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combines multiple linters and code analyzers for both code and documentation. Once you're done with your changes, submit a pull request.
-
-### Contributing to Pro components
-
-All of Karafka components are open-source. However, the `Pro` components are licenses under `LICENSE-COMM`.
-
-By sending a pull request to the pro components, you are agreeing to transfer the copyright of your code to Maciej Mensfeld.
-
-## Questions
-
-If you have any questions, create an [issue](https://github.com/karafka/karafka/issues) (protip: do a quick search first to see if someone else didn't ask the same question before!).
-You can also reach us at contact@karafka.io.

data/Gemfile

@@ -1,28 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-gemspec
-
-# Karafka gem does not require activejob, karafka-web or fugit to work
-# They are added here because they are part of the integration suite
-# Since some of those are only needed for some specs, they should never be required automatically
-group :integrations, :test do
-  gem 'fugit', require: false
-  gem 'rspec', require: false
-  gem 'stringio'
-  gem 'warning'
-end
-
-group :integrations do
-  gem 'activejob', require: false
-  gem 'karafka-testing', '>= 2.5.0', require: false
-  gem 'karafka-web', '>= 0.11.1', require: false
-end
-
-group :test do
-  gem 'byebug'
-  gem 'factory_bot'
-  gem 'ostruct'
-  gem 'simplecov'
-end

data/Gemfile.lock

@@ -1,173 +0,0 @@
-PATH
-  remote: .
-  specs:
-    karafka (2.5.2)
-      base64 (~> 0.2)
-      karafka-core (>= 2.5.6, < 2.6.0)
-      karafka-rdkafka (>= 0.22.0)
-      waterdrop (>= 2.8.9, < 3.0.0)
-      zeitwerk (~> 2.3)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    activejob (8.1.1)
-      activesupport (= 8.1.1)
-      globalid (>= 0.3.6)
-    activesupport (8.1.1)
-      base64
-      bigdecimal
-      concurrent-ruby (~> 1.0, >= 1.3.1)
-      connection_pool (>= 2.2.5)
-      drb
-      i18n (>= 1.6, < 2)
-      json
-      logger (>= 1.4.2)
-      minitest (>= 5.1)
-      securerandom (>= 0.3)
-      tzinfo (~> 2.0, >= 2.0.5)
-      uri (>= 0.13.1)
-    base64 (0.3.0)
-    bigdecimal (3.3.1)
-    byebug (12.0.0)
-    concurrent-ruby (1.3.5)
-    connection_pool (2.5.4)
-    diff-lcs (1.6.2)
-    docile (1.4.1)
-    drb (2.2.3)
-    erubi (1.13.1)
-    et-orbi (1.4.0)
-      tzinfo
-    factory_bot (6.5.6)
-      activesupport (>= 6.1.0)
-    ffi (1.17.2)
-    ffi (1.17.2-aarch64-linux-gnu)
-    ffi (1.17.2-aarch64-linux-musl)
-    ffi (1.17.2-arm-linux-gnu)
-    ffi (1.17.2-arm-linux-musl)
-    ffi (1.17.2-arm64-darwin)
-    ffi (1.17.2-x86-linux-gnu)
-    ffi (1.17.2-x86-linux-musl)
-    ffi (1.17.2-x86_64-darwin)
-    ffi (1.17.2-x86_64-linux-gnu)
-    ffi (1.17.2-x86_64-linux-musl)
-    fugit (1.12.1)
-      et-orbi (~> 1.4)
-      raabro (~> 1.4)
-    globalid (1.3.0)
-      activesupport (>= 6.1)
-    i18n (1.14.7)
-      concurrent-ruby (~> 1.0)
-    json (2.15.2)
-    karafka-core (2.5.7)
-      karafka-rdkafka (>= 0.20.0)
-      logger (>= 1.6.0)
-    karafka-rdkafka (0.22.2)
-      ffi (~> 1.15)
-      json (> 2.0)
-      logger
-      mini_portile2 (~> 2.6)
-      rake (> 12)
-    karafka-rdkafka (0.22.2-aarch64-linux-gnu)
-      ffi (~> 1.15)
-      json (> 2.0)
-      logger
-      mini_portile2 (~> 2.6)
-      rake (> 12)
-    karafka-rdkafka (0.22.2-arm64-darwin)
-      ffi (~> 1.15)
-      json (> 2.0)
-      logger
-      mini_portile2 (~> 2.6)
-      rake (> 12)
-    karafka-rdkafka (0.22.2-x86_64-linux-gnu)
-      ffi (~> 1.15)
-      json (> 2.0)
-      logger
-      mini_portile2 (~> 2.6)
-      rake (> 12)
-    karafka-rdkafka (0.22.2-x86_64-linux-musl)
-      ffi (~> 1.15)
-      json (> 2.0)
-      logger
-      mini_portile2 (~> 2.6)
-      rake (> 12)
-    karafka-testing (2.5.4)
-      karafka (>= 2.5.0, < 2.6.0)
-      waterdrop (>= 2.8.0)
-    karafka-web (0.11.3)
-      erubi (~> 1.4)
-      karafka (>= 2.5.0, < 2.6.0)
-      karafka-core (>= 2.5.0, < 2.6.0)
-      roda (~> 3.68, >= 3.69)
-      tilt (~> 2.0)
-    logger (1.7.0)
-    mini_portile2 (2.8.9)
-    minitest (5.26.0)
-    ostruct (0.6.3)
-    raabro (1.4.0)
-    rack (3.2.3)
-    rake (13.3.0)
-    roda (3.97.0)
-      rack
-    rspec (3.13.2)
-      rspec-core (~> 3.13.0)
-      rspec-expectations (~> 3.13.0)
-      rspec-mocks (~> 3.13.0)
-    rspec-core (3.13.6)
-      rspec-support (~> 3.13.0)
-    rspec-expectations (3.13.5)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.13.0)
-    rspec-mocks (3.13.6)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.13.0)
-    rspec-support (3.13.6)
-    securerandom (0.4.1)
-    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)
-    stringio (3.1.7)
-    tilt (2.6.1)
-    tzinfo (2.0.6)
-      concurrent-ruby (~> 1.0)
-    uri (1.0.4)
-    warning (1.5.0)
-    waterdrop (2.8.12)
-      karafka-core (>= 2.4.9, < 3.0.0)
-      karafka-rdkafka (>= 0.20.0)
-      zeitwerk (~> 2.3)
-    zeitwerk (2.7.3)
-
-PLATFORMS
-  aarch64-linux-gnu
-  aarch64-linux-musl
-  arm-linux-gnu
-  arm-linux-musl
-  arm64-darwin
-  ruby
-  x86-linux-gnu
-  x86-linux-musl
-  x86_64-darwin
-  x86_64-linux-gnu
-  x86_64-linux-musl
-
-DEPENDENCIES
-  activejob
-  byebug
-  factory_bot
-  fugit
-  karafka!
-  karafka-testing (>= 2.5.0)
-  karafka-web (>= 0.11.1)
-  ostruct
-  rspec
-  simplecov
-  stringio
-  warning
-
-BUNDLED WITH
-   2.7.1

data/Rakefile

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

data/SECURITY.md

@@ -1,23 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-Please refer to the Karafka [EOL documentation](https://karafka.io/docs/Versions-Lifecycle-and-EOL/) page for detailed information on which versions are actively supported with security updates.
-
-## Reporting a Vulnerability
-
-If you have identified a potential security vulnerability in our projects, we encourage you to report it immediately. We take all reports of security issues seriously and will work diligently to address them.
-
-To report a vulnerability, please send an email directly to contact@karafka.io.
-
-We understand the importance of addressing security vulnerabilities promptly. You can expect a reply from us within 2 working days of your report. This initial response will confirm receipt of your report.
-
-After acknowledging your report, we will:
-
-- Evaluate the reported vulnerability in the context of our project.
-- Provide you with regular updates on our progress.
-- Upon completing our assessment, we will inform you of the outcome. This includes whether the vulnerability will be accepted or declined for further action.
-
-Your report will be kept confidential and not disclosed to third parties without your consent, except as required by law.
-
-We appreciate your assistance in keeping our projects and their users safe by responsibly reporting vulnerabilities. Together, we can maintain a high standard of security for our community.

data/bin/benchmarks

@@ -1,99 +0,0 @@
-#!/usr/bin/env ruby
-
-# Runner for running given benchmark cases
-# Some of the cases require pre-populated data and we populate this in places that need it
-# In other cases we generate this data in a background process, so the partitions data stream
-# is consistent and we don't end up consuming huge batches of a single partition.
-
-require 'open3'
-require 'pathname'
-
-$LOAD_PATH.unshift(File.dirname(__FILE__))
-$LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..'))
-
-ROOT_PATH = Pathname.new(File.expand_path(File.join(File.dirname(__FILE__), '../')))
-
-BENCHMARK_TOPICS = {
-  'benchmarks_00_01' => 1,
-  'benchmarks_00_05' => 5,
-  'benchmarks_01_05' => 5,
-  'benchmarks_00_10' => 10
-}
-
-# Load all the benchmarks
-benchmarks = Dir[ROOT_PATH.join('spec/benchmarks/**/*.rb')]
-
-# If filter is provided, apply
-benchmarks.delete_if { |name| !name.include?(ARGV[0]) } if ARGV[0]
-
-raise ArgumentError, "No benchmarks with filter: #{ARGV[0]}" if benchmarks.empty?
-
-# We may skip seeding if we are running the benchmarks multiple times, then since we do not
-# commit offsets we can skip generating more data
-if ENV['SEED']
-  require 'spec/benchmarks_helper'
-
-  # We need to setup karafka here to have producer for data seeding
-  setup_karafka
-
-  # This takes some time but needs to run only once per benchmark session
-  puts 'Seeding benchmarks data...'
-
-  producer = Karafka::App.producer
-
-  # We make our data json compatible so we can also benchmark serialization
-  elements = Array.new(100_000) { { a: :b }.to_json }
-
-  topics = Karafka::Admin.cluster_info.topics.map { |details| details.fetch(:topic_name) }
-
-  BENCHMARK_TOPICS.each do |topic_name, partitions_count|
-    ::Karafka::Admin.delete_topic(topic_name) if topics.include?(topic_name)
-    ::Karafka::Admin.create_topic(topic_name, partitions_count, 1)
-  end
-
-  # We do not populate data of benchmarks_0_10 as we use it with life-stream data only
-  %w[
-    benchmarks_00_01
-    benchmarks_00_05
-  ].each do |topic_name|
-    partitions_count = topic_name.split('_').last.to_i
-
-    partitions_count.times do |partition|
-      puts "Seeding #{topic_name}:#{partition}"
-
-      elements.each_slice(10_000) do |data_slice|
-        data = data_slice.map do |data|
-          { topic: topic_name, payload: data, partition: partition }
-        end
-
-        producer.buffer_many(data)
-        producer.flush_sync
-      end
-    end
-  end
-end
-
-# Selects requested benchmarks and runs them one after another
-benchmarks.each do |benchmark_path|
-  puts "Running #{benchmark_path.gsub("#{ROOT_PATH}/spec/benchmarks/", '')}"
-
-  benchmark = "bundle exec ruby -r ./spec/benchmarks_helper.rb #{benchmark_path}"
-
-  Open3.popen3(benchmark) do |stdin, stdout, stderr, thread|
-    t1 = Thread.new do
-      while line = stdout.gets
-        puts(line)
-      end
-    rescue IOError
-    end
-
-    t2 = Thread.new do
-      while line = stderr.gets
-        puts(line)
-      end
-    rescue IOError
-    end
-
-    thread.join
-  end
-end

data/bin/clean_kafka

@@ -1,43 +0,0 @@
-#!/usr/bin/env ruby
-
-# A script that removes most of the auto-generated Kafka topics with their data
-# Useful when having long-running Kafka instance that cannot be fully nuked after running specs
-
-# We use the same convention in other framework components (web, waterdrop), so it removes all of
-# them as well.
-
-require_relative '../spec/integrations_helper.rb'
-
-setup_karafka
-
-topics_for_removal = []
-
-Karafka::Admin.cluster_info.topics.each do |topic|
-  topic_name = topic[:topic_name]
-
-  next unless topic_name.start_with?('it-')
-
-  topics_for_removal << topic_name
-end
-
-THREADS_COUNT = 3
-QUEUE = SizedQueue.new(THREADS_COUNT)
-TOPICS_TO_REMOVAL_COUNT = topics_for_removal.size
-
-threads = Array.new(THREADS_COUNT) do
-  Thread.new do
-    while topic_name = QUEUE.pop
-      puts "Removing topic: #{topic_name} (#{topics_for_removal.count} left)"
-      Karafka::Admin.delete_topic(topic_name)
-    end
-  end
-end
-
-while topics_for_removal.size.positive?
-  topic_name = topics_for_removal.pop
-
-  QUEUE << topic_name
-end
-
-QUEUE.close
-threads.each(&:join)

data/bin/create_token

@@ -1,22 +0,0 @@
-#!/usr/bin/env ruby
-
-require 'openssl'
-require 'base64'
-require 'json'
-require 'date'
-
-PRIVATE_KEY_LOCATION = File.join(Dir.home, '.ssh', 'karafka-pro', 'id_rsa')
-
-# Name of the entity that acquires the license
-ENTITY = ARGV[0]
-
-raise ArgumentError, 'Entity missing' if ENTITY.nil? || ENTITY.empty?
-
-pro_token_data = { entity: ENTITY }
-
-# This code uses my private key to generate a new token for Karafka Pro capabilities
-private_key = OpenSSL::PKey::RSA.new(File.read(PRIVATE_KEY_LOCATION))
-
-bin_key = private_key.private_encrypt(pro_token_data.to_json)
-
-puts Base64.encode64(bin_key)