-
Notifications
You must be signed in to change notification settings - Fork 5.8k
executor: run start-phase operations (epic #14081, lot 1) #14274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ndeloof
wants to merge
5
commits into
docker:main
Choose a base branch
from
ndeloof:executor-start-phase
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+850
−27
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d28d74d
feat: executor runs start-phase operations
ndeloof 0c39d42
fix: a failed pre_start/start no longer lets its dependent run
ndeloof 219f34c
docs: spell out that the ctx.Err() guards narrow the race, not close it
ndeloof b1a06a5
fix: execRunPreStart bails out on a canceled context
ndeloof de7ce85
fix: release startMx with defer in the enriched execStartContainer path
ndeloof File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[medium] A failing
OpRunPreStartemits anapi.Errorevent with no precedingWorking/StartingeventtriggersWorkingreturnstrueonly forOpStartContainerin agroupStartgroup:This is intentional for the happy path — pre_start hooks run silently before the
Startingevent fires. But whenOpRunPreStartitself fails (e.g. the hook-runner container is not found, or the hook exits non-zero),run()callsonNodeError, which emits anapi.Errorresource event ongs.eventName. NoWorkingevent (statusStarting) was ever emitted for this group, becausetriggersWorkingreturnedfalseforOpRunPreStart.Progress-bar consumers tracking
Working → Done / Errorstate transitions will see a bareErrorfor a container they had never seen transition toStarting. The resource appears in an error state from nowhere, which can cause progress-display UIs to render incorrectly (the container never appeared "starting" before flipping to an error).The imperative engine's
startServicealways emits aStartingevent before any outcome; thegroupStart/onNodeErrorpath has no equivalent guard.Suggested fix: track whether the group's
Workingevent has fired (e.g. aworkingEmitted boolfield ongroupState), and emit an implicitStartingevent inonNodeErrorwhen the group kind isgroupStartand!gs.workingEmitted— keeping the event sequence well-formed even when pre_start fails beforeContainerStartis reached.