Repository navigation
Conversation
Part of storing the last successful check-in time on monitor incidents, so incident occurrences don't need a check-in lookup. A race can leave an open incident on a monitor environment whose status is OK. The next failure reuses that incident through get_or_create, so its last successful time was stale. This sets it from the same lookup used for new incidents.
This branch has not been deployed
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
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.
Part of storing the last successful check-in time on monitor incidents, so incident occurrences don't need a check-in lookup.
A race can leave an open incident on a monitor environment whose status is OK. The next failure reuses that incident through
get_or_create, so its last successful time was stale. This sets it from the same lookup used for new incidents.