-
Notifications
You must be signed in to change notification settings - Fork 192
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
fix: add support for Sidekiq 8 #1444
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @dmathieu! This is looking good. I have a suggestion on how to skip the Sidekiq 8 suite for Ruby 3.1.
Co-authored-by: Kayla Reopelle <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @dmathieu.
...on/sidekiq/lib/opentelemetry/instrumentation/sidekiq/middlewares/client/tracer_middleware.rb
Outdated
Show resolved
Hide resolved
...on/sidekiq/lib/opentelemetry/instrumentation/sidekiq/middlewares/server/tracer_middleware.rb
Outdated
Show resolved
Hide resolved
…kiq/middlewares/server/tracer_middleware.rb Co-authored-by: Troels Thomsen <[email protected]>
…kiq/middlewares/client/tracer_middleware.rb Co-authored-by: Troels Thomsen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this fix.
I think longer term we need to make some SDK changes to mitigate this. The timestamp should probably be a Ruby Time object to mitigate these kinds of weird cases that would result in overflows.
This adds support for Sidekiq 8 in the tests.
It also fixes an error where the event timestamp was provided in milliseconds, and therefore caused range errors when being converted into OTLP because the bignum was too large.