Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle Pulsar Token bug in affected versions #221

Conversation

entvex
Copy link
Contributor

@entvex entvex commented May 30, 2024

Description

The commit updates the used images of ToxiProxy and Pulsar in tests from versions 2.7.0 and 3.1.3 to 2.9.0 and 3.2.3 respectively to keep up with the latest versions.

The issue arises because Apache Pulsar incorrectly treats seconds as milliseconds in specific versions. To address this, we multiply the value by 1000 when using affected versions.

Finally, I added a missing cancellation token in ConnectionPool.

Testing

All tests now works on the newest Apache Pulsar version

The commit updates the used images of ToxiProxy and Pulsar in tests from versions 2.7.0 and 3.1.3 to 2.9.0 and 3.2.3 respectively to keep up with the latest versions.

The issue arises because Apache Pulsar incorrectly treats seconds as milliseconds in specific versions. To address this, we multiply the value by 1000 when using affected versions.

Finally, I added a missing cancellation token in ConnectionPool.
@entvex entvex added the enhancement New feature or request label May 30, 2024
@entvex entvex self-assigned this May 30, 2024
@entvex entvex marked this pull request as draft May 30, 2024 17:25
@entvex entvex closed this Jun 7, 2024
@entvex entvex deleted the Apache-Pulsar-incorrectly-treats-seconds-as-milliseconds branch June 10, 2024 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant