feat(Task Resolution): Event Log Based Task Resolution #1039
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
SujitMBRDI
approved these changes
Aug 26, 2024
…rator finished task event log - add a secondary Health Check schedule for gates making sure to still discover missing tasks - added finished task event log on Orchestrator - added result state search endpoint for healthcheck on Orchestrator - changed the gate's resolution logic to use the event log - added Orchestrator tests for event log - adapted Gate tests accordingly
nicoprow
force-pushed
the
feat/event-log-based-task-resolution
branch
from
f0367c9 to
33a80ec
Compare
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.
Description
Gates now resolve tasks by using a new Orchestrator finished task event log
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: