Use a consistent timebase when evaluating soft/hard TTLs.#391
Merged
jpd236 merged 1 commit intogoogle:masterfrom Jan 26, 2021
Merged
Use a consistent timebase when evaluating soft/hard TTLs.#391jpd236 merged 1 commit intogoogle:masterfrom
jpd236 merged 1 commit intogoogle:masterfrom
Conversation
Previously, we'd evaluate whether a cache entry was valid per these TTLs using two different checks against the current system time. This could result in a spurious trigger of soft TTL logic if the first time check occurs before the soft TTL expiry but the second occurs after it, and the hard and soft TTL are identical. Unit tests are omitted since we don't have an easy way to mock the clock with the current architecture. This could be improved in the future.
Collaborator
Author
|
PR reviewed offline by @uhager - going ahead and merging. |
This was referenced Mar 9, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously, we'd evaluate whether a cache entry was valid per these TTLs using two different checks against the current system time. This could result in a spurious trigger of soft TTL logic if the first time check occurs before the soft TTL expiry but the second occurs after it, and the hard and soft TTL are identical.
Unit tests are omitted since we don't have an easy way to mock the clock with the current architecture. This could be improved in the future.
Fixes #388