kafka_int_tests::cluster_sasl_scram_over_mtls_nodejs_and_python attempt to fix intermittent failure

[rukai]

Attempts to fix the below failure that occurred in https://github.com/shotover/shotover-proxy/actions/runs/11964647835/job/33357613709

kafka_int_tests::cluster_sasl_scram_over_mtls_nodejs_and_python ---
{"level":"WARN","timestamp":"2024-11-22T01:33:58.889Z","logger":"kafkajs","message":"KafkaJS v2.0.0 switched default partitioner. To retain the same partitioning behavior as in previous versions, create the producer with the option \"createPartitioner: Partitioners.LegacyPartitioner\". See the migration guide at https://kafka.js.org/docs/migration-guide-v2.0.0#producer-new-default-partitioner for details. Silence this warning by setting the environment variable \"KAFKAJS_NO_PARTITIONER_WARNING=1\""}
{"level":"ERROR","timestamp":"2024-11-22T01:33:59.862Z","logger":"kafkajs","message":"[Connection] Response Metadata(key: 3, version: 6)","broker":"127.0.0.1:9192","clientId":"nodejs-client","error":"This server does not host this topic-partition","correlationId":4,"size":83}
{"level":"ERROR","timestamp":"2024-11-22T01:34:00.245Z","logger":"kafkajs","message":"[Connection] Response GroupCoordinator(key: 10, version: 2)","broker":"127.0.0.1:9192","clientId":"nodejs-client","error":"The group coordinator is not available","correlationId":5,"size":55}
{"level":"ERROR","timestamp":"2024-11-22T01:34:00.527Z","logger":"kafkajs","message":"[Connection] Response GroupCoordinator(key: 10, version: 2)","broker":"127.0.0.1:9192","clientId":"nodejs-client","error":"The group coordinator is not available","correlationId":6,"size":55}
downloading uv 0.4.6 x86_64-unknown-linux-gnu
Using Python 3.12.5
Creating virtualenv at: .venv
Installed 1 package in 2ms
<BrokerConnection node_id=bootstrap-0 host=127.0.0.1:9192 <authenticating> [IPv4 ('127.0.0.1', 9192)]>: Exchanging credentials in the clear
<BrokerConnection node_id=0 host=127.0.0.1:9192 <authenticating> [IPv4 ('127.0.0.1', 9192)]>: Exchanging credentials in the clear
<BrokerConnection node_id=bootstrap-0 host=127.0.0.1:9192 <authenticating> [IPv4 ('127.0.0.1', 9192)]>: Exchanging credentials in the clear
<BrokerConnection node_id=0 host=127.0.0.1:9192 <authenticating> [IPv4 ('127.0.0.1', 9192)]>: Exchanging credentials in the clear
Traceback (most recent call last):
  File "/home/runner/work/shotover-proxy/shotover-proxy/test-helpers/src/connection/kafka/python/main.py", line 41, in <module>
    main()
  File "/home/runner/work/shotover-proxy/shotover-proxy/test-helpers/src/connection/kafka/python/main.py", line 22, in main
    producer.send('python_test_topic', b'some_message_bytes').get(timeout=30)
  File "/home/runner/work/shotover-proxy/shotover-proxy/test-helpers/src/connection/kafka/python/.venv/lib/python3.12/site-packages/kafka/producer/future.py", line 63, in get
    raise self.exception # pylint: disable-msg=raising-bad-type
    ^^^^^^^^^^^^^^^^^^^^
kafka.errors.UnknownTopicOrPartitionError: [Error 3] UnknownTopicOrPartitionError
thread 'kafka_int_tests::cluster_sasl_scram_over_mtls_nodejs_and_python' panicked at /home/runner/work/shotover-proxy/shotover-proxy/test-helpers/src/lib.rs:51:9:
command /home/runner/work/shotover-proxy/shotover-proxy/target/uv/bin/uv ["run", "main.py", "{\n    'bootstrap_servers': [\"127.0.0.1:9192\"],\n    'security_protocol': \"SASL_PLAINTEXT\",\n    'sasl_mechanism': \"SCRAM-SHA-256\",\n    'sasl_plain_username': \"super_user\",\n    'sasl_plain_password': \"super_password\",\n}"] failed. See above output.
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: test_helpers::run_command_async::{{closure}}
   3: <tokio::time::timeout::Timeout<T> as core::future::future::Future>::poll
   4: lib::kafka_int_tests::cluster_sasl_scram_over_mtls_nodejs_and_python::{{closure}}
   5: tokio::runtime::runtime::Runtime::block_on
   6: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I cant reproduce the issue locally, so I am not able to verify this fixes this issue since it is rare.

[codspeed-hq]

CodSpeed Performance Report

Merging #1841 will not alter performance

_{Comparing rukai:attempt_to_fix_intermittent_failure (0162d54) with main (27248c2)}

Summary

✅ 38 untouched benchmarks