This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Fix deadman notification delay (EXPOSUREAPP-7955) #3533
Merged
Conversation
This file contains 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
chiljamgossow
added
maintainers
chiljamgossow
changed the title
|
Kudos, SonarCloud Quality Gate passed! |
AlexanderAlferov
approved these changes
Jun 23, 2021
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
use createdAt timestamp to calculate delay of notification (not the package date)
Scenario: metered connection -> only day packages. In the morning of 06/23 it will download package 06/22. Before it would take the date at start of the day and plan a notification in 36h minus the age of the downladed package - which is already 24h hours old when it was downloaded. So 12h later the day the user gets the notification - despite having a daily download