Check if key is in roots map of Processor #718
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
asubrocky
reviewed
Jul 26, 2023
asubrocky
previously approved these changes
Jul 26, 2023
asubrocky
approved these changes
Jul 26, 2023
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.
Before notifying, we should ensure the key is in the roots map to prevent attempts to notify check run on invalid, empty repo metadata. There is a chance the root map can miss a key if multiple revisions come in quickly and a new Processor for the latest revision is receiving a signal on an old revision. We shouldn't care about this signal since we already perform a clean defer to cancel those check runs on shutdown of the old revision Processor.