karafka 2.4.1 → 2.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7f3d5fa334ede552c2b0097acf16a942318ef648bcdbdcb0e84ffefcd5e65772
-  data.tar.gz: d800e8e25a62df01000dee9e3ce5904f3ddf632f66ac49e0c71dde3a6702209b
+  metadata.gz: 5eb2aeb0bd3cd0d50d70b0fd792e8290315f3131222d3befab9b5a05bd478e07
+  data.tar.gz: 27b4d40fe18c3daf87ea3f2b601487d6cad5a766121374772179fc5fb3049f75
 SHA512:
-  metadata.gz: ac438f23ca449023ff9537a5aa007879f2420dfdfe1cd81c1715322cfea53af8112cdf77663547155a40ba4e154cbc8e9c81df23dff9a6f843bb0601395b7271
-  data.tar.gz: 3e267b623cee9b649182ac08d34a68780e696e9ba24fda448caecb762ebf726f436b1b5b3415240f8409b4c7b66fc62c39c319c58128e429580f3468db1e152e
+  metadata.gz: af5c4030ccd1f881558df342c3936152efc6183ccc6238246a327d6da8b716e65e3e56ec198a708b87f292bd01d9e426fb64b3c4b9a4f5b40111ee68795ec050
+  data.tar.gz: 7d04bb79ea03cc5eedf7a8e9ecd62abc0ff2b48aea2e4df929d691b931b728017adf843aec5c248a6d4e8b42dd1957c798e799b9df82ae009795ae6b414532ac

checksums.yaml.gz.sig

@@ -1,2 +1,4 @@
-�c�}�F�V�9)��KU��dtQЛA!�~���[O�hW�~j�mb;�8i��&&�'[�vj��I4]s��l �5\ݫ�s�I�C~��kٓ8B݈$���03k�}�0`i3�G�3���O�S��}|e�L5/%E����֣[�%~=�ӌN>�h��#�Q�9f����P5�sv��Pء)�+<ںl?|�����܂Ι�E�*���R#>�,�o�H}��1��\=��D�I���J����q%����G�d����U���A��~��y?��SBw�bs�La��qn�Fp5�n_@i�Ɗ��N
-�IG���7|�!�!8�p�g��?�+��$� ��W����'�<�l�
�]N&ԫ��D�������@�%JK�k����
+_�l*�}3r�;�z!����O4i�䪐U�m��.�Q}�N�*�<_�l�֑Ó|-n�M����\N��B(�Ot��>ß�(��2E%P�ɟY�l[����r��v�ͤ�ō�ܤN�
+�}�F��Ј-Ó�����{L�&�.��"z:q�
+P�0=�6J��,��٭qF�U��=�)��S�|��\ YW`��FdKT��=��*��	V��L
+�����x�?�>��+g�,S�=�N����0�-��V��0�}��[�������U��	�[_�Hȳ-ൠo��{<�f��)�TI�
�{���2�g��?���{��6T�p�������x�`rg����ZD�}�蕽n�焫X�]�I�Qi}��V�

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Karafka framework changelog
 
+## 2.4.2 (2024-05-14)
+- [Enhancement] Validate ActiveJob adapter custom producer format.
+- [Fix] Internal seek does not resolve the offset correctly for time based lookup.
+
 ## 2.4.1 (2024-05-10)
 - [Enhancement] Allow for usage of producer variants and alternative producers with ActiveJob Jobs (Pro).
 - [Enhancement] Support `:earliest` and `:latest` in `Karafka::Admin#seek_consumer_group`.
@@ -70,6 +74,10 @@ This release contains **BREAKING** changes. Make sure to read and apply upgrade
 
 Available [here](https://karafka.io/docs/Upgrades-2.4/).
 
+## 2.3.4 (2024-04-11)
+
+- [Fix] Seek consumer group on a topic level is updating only recent partition.
+
 ## 2.3.3 (2024-02-26)
 - [Enhancement] Routing based topics allocation for swarm (Pro)
 - [Enhancement] Publish the `-1` shutdown reason status for a non-responding node in swarm.

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    karafka (2.4.1)
+    karafka (2.4.2)
       base64 (~> 0.2)
       karafka-core (>= 2.4.0, < 2.5.0)
       waterdrop (>= 2.7.0, < 3.0.0)

data/config/locales/errors.yml

@@ -144,6 +144,7 @@ en:
       dispatch_many_method_format: needs to be either :produce_many_async or :produce_many_sync
       partitioner_format: 'needs to respond to #call'
       partition_key_type_format: 'needs to be either :key or :partition_key'
+      producer_format: 'needs to respond to #call'
 
     test:
       missing: needs to be present

data/lib/karafka/connection/client.rb

@@ -402,7 +402,9 @@ module Karafka
           # then seek to the appropriate message
           # We set the timeout to 2_000 to make sure that remote clusters handle this well
           real_offsets = @wrapped_kafka.offsets_for_times(tpl)
-          detected_partition = real_offsets.to_h.dig(message.topic, message.partition)
+          # We always ask for one partition, so result will contain array with only one element
+          # that is the partition we were interested it regardless its number
+          detected_partition = real_offsets.to_h.dig(message.topic, 0)
 
           # There always needs to be an offset. In case we seek into the future, where there
           # are no offsets yet, we get -1 which indicates the most recent offset

data/lib/karafka/pro/active_job/job_options_contract.rb

@@ -25,6 +25,7 @@ module Karafka
           ).fetch('en').fetch('validations').fetch('job_options')
         end
 
+        optional(:producer) { |val| val.nil? || val.respond_to?(:call) }
         optional(:partitioner) { |val| val.respond_to?(:call) }
         optional(:partition_key_type) { |val| %i[key partition_key partition].include?(val) }
         optional(:dispatch_method) do |val|

data/lib/karafka/templates/karafka.rb.erb

@@ -59,7 +59,7 @@ class KarafkaApp < Karafka::App
     )
   )
 
-  # You can subscribe to all consumer related errors and record/track then that way
+  # You can subscribe to all consumer related errors and record/track them that way
   #
   # Karafka.monitor.subscribe 'error.occurred' do |event|
   #   type = event[:type]
@@ -68,7 +68,7 @@ class KarafkaApp < Karafka::App
   #   ErrorTracker.send_error(error, type, details)
   # end
 
-  # You can subscribe to all producer related errors and record/track then that way
+  # You can subscribe to all producer related errors and record/track them that way
   # Please note, that producer and consumer have their own notifications pipeline so you need to
   # setup error tracking independently for each of them
   #

data/lib/karafka/version.rb

@@ -3,5 +3,5 @@
 # Main module namespace
 module Karafka
   # Current Karafka version
-  VERSION = '2.4.1'
+  VERSION = '2.4.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: karafka
 version: !ruby/object:Gem::Version
-  version: 2.4.1
+  version: 2.4.2
 platform: ruby
 authors:
 - Maciej Mensfeld
@@ -35,7 +35,7 @@ cert_chain:
   AnG1dJU+yL2BK7vaVytLTstJME5mepSZ46qqIJXMuWob/YPDmVaBF39TDSG9e34s
   msG3BiCqgOgHAnL23+CN3Rt8MsuRfEtoTKpJVcCfoEoNHOkc
   -----END CERTIFICATE-----
-date: 2024-05-10 00:00:00.000000000 Z
+date: 2024-05-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: base64