Avoid panic in an internal base_cache::Clocks::to_std_instant
method
#477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #472.
This PR should avoid occasional panic in an internal
base_cache::Clocks::to_std_instant
method by using zeroDuration
ifchecked_duration_since
method fails.I could not figure out why the specific call of
checked_duration_since
method can fail. I might have overlooked something inmoka
's code, or maybequanta::Instant
can return not a monotonically increasing time on some CPUs?