This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Fix RiskLevelCalculationTask not being executed if no new match was found (EXPOSUREAPP-3849) #1657
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
d4rken
added
bug
…en-if-no-match # Conflicts: # Corona-Warn-App/src/main/java/de/rki/coronawarnapp/storage/TracingRepository.kt
BMItr
reviewed
Nov 18, 2020
|
|
||
| fun Throwable.report( | ||
| exceptionCategory: ExceptionCategory, | ||
| prefix: String?, | ||
| suffix: String? | ||
| ) { | ||
| reportProblem(tag = prefix, info = suffix) |
|
Kudos, SonarCloud Quality Gate passed!
|
d4rken
changed the title
ralfgehrer
deleted the
fix/3849-execute-riskcalculation-even-if-no-match
branch
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.
The RiskLevelCalculationTask was not being executed if the provided key files didn't result in a new exposure summary state.
For some reasons this was not a visible issue before, but unrelated changes have made this issue visible now.
Testing