Make expiresAt persistent & adjustable based on Pod time and activatedAt fixed again #555
Conversation
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
…or clock drift Round alert configuration times to the nearest minute
itsmojo
changed the title
dthornley
pushed a commit
to dthornley/rileylink_ios
that referenced
this pull request
Oct 2, 2019
…dAt fixed again (ps2#555) * Adjust activatedAt (and thus expiresAt) on Pod responses to account for clock drift Round alert configuration times to the nearest minute * Fixed and improved logic & comments for when to rewrite activatedAt * Make activatedAt fixed again and expiresAt persistent & changeable * Set expiresAt appropriately when initializing from persistent storage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.