-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Cache::get
method sometimes panics due to an integer overflow in quanta::instant::Instant::now
#119
Comments
Yeah. It looks like so. From your stack trace, I see metrics-rs/quanta#61 (comment)
As a workaround, I am going to add a Cargo feature to Moka to opt-out Quanta. Also, when I have more time, I will try to reproduce the issue by using AMD based instance at Amazon EC2. |
Memo: I could reuse the codes here: #39 |
Working on this workaround via #121. Not quite finished yet. |
Hi @BrynCooke, I have published Moka v0.8.3 to crates.io. Now you can opt out Quanta crate by adding Hope this helps. I will keep this GH Issue open until Quanta addresses the issue. |
Cache::get
method sometimes panics in debug build due to an integer overflow in quanta::instant::Instant::now
Cache::get
method sometimes panics in due to an integer overflow in quanta::instant::Instant::now
@tatsuya6502 Thanks for sorting this out so quickly! |
Cache::get
method sometimes panics in due to an integer overflow in quanta::instant::Instant::now
Cache::get
method sometimes panics due to an integer overflow in quanta::instant::Instant::now
Hi @BrynCooke — I have published Moka v0.8.4 to crates.io. It depends on the latest Quanta v0.10.0 that has the fix for the panic issue. Please try Moka v0.8.4 when you have time. Thanks! |
I had a go and can no longer reproduce the issue. Thanks @tatsuya6502! |
Moka has a dependency on Quanta which had an issue with AMD hardware. This is now fixed via [Moka-#119](moka-rs/moka#119).
Moka has a dependency on Quanta which had an issue with AMD hardware. This is now fixed via [Moka-#119](moka-rs/moka#119).
Moka has a dependency on Quanta which had an issue with AMD hardware. This is now fixed via [Moka-#119](moka-rs/moka#119). Co-authored-by: bryn <bryn@apollographql.com>
Moka has a dependency on Quanta which had an issue with AMD hardware. This is now fixed via [Moka-#119](moka-rs/moka#119).
Glad to hear the issue is fixed. 👍🏻 |
This issue was reported by @BrynCooke on May 10, 2022 UTC via #113 (comment)
I have been hitting this issue and am able to reproduce by running an integration test in a loop.
Looks like it is possibly related to this: metrics-rs/quanta#61
The stacktrace is as follows:
The number of times needed to hit this is very low. Sometimes it happens within 10 invocations, sometimes 100.
The text was updated successfully, but these errors were encountered: