Reset trace and transaction for sidekiq-cron#2446
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2446 +/- ##
==========================================
- Coverage 98.16% 98.13% -0.04%
==========================================
Files 126 126
Lines 4741 4761 +20
==========================================
+ Hits 4654 4672 +18
- Misses 87 89 +2
|
8754868 to
1fe8563
Compare
|
@solnic Any ideas or input for the if Version >= 2
def enqueue!
...
end
else
def enque!
...
end
endwith the exact same content of the two methods. |
solnic
left a comment
There was a problem hiding this comment.
Some small things to improve/simplify :)
Remove unneeded exception alloc Set root op instead of nested spans Initial commit Add a spec This is ugly - Want input Inline allocation Inline more Add changelog entry Feedback on PR
f8243d7 to
f9bce57
Compare
Replied to some, and adjusted for others! @solnic |
|
@solnic That's weird... Let me just validate tomorrow, and see what might go wrong. |
|
@solnic Are you on latest commit? I've just tried this here, and my cron jobs look like this (Just from the
I'm not sure how to proceed debugging here. |
OK I tried again and I no longer see this issue! 🎉 |
|
FWIW, we have seen this kind of error with making our cron fails. Updating sidekiq-cron to 2.0 fixes the issue. |


Description
Adds a new transaciton and reset for Sidekiq cron #enque!, so that they are not forever-running traces in the web view.
Depends on #2403.Fixes #2391