Conversation
akashdw
force-pushed
the
ad/step-phase-timeouts
branch
from
September 16, 2026 16:36
784da2e to
01d641d
Compare
akashdw
force-pushed
the
ad/step-phase-timeouts
branch
from
September 16, 2026 17:42
01d641d to
dcf9e67
Compare
ykitaev
approved these changes
Sep 16, 2026
rdeepak2002
reviewed
Sep 19, 2026
| @EqualsAndHashCode | ||
| public class StepTimeouts { | ||
| /** Timeout for the whole step instance, in seconds or as a duration string. */ | ||
| @TimeoutConstraint private final ParsableLong step; |
Collaborator
There was a problem hiding this comment.
optional nit: I was curious on your thoughts about calling this overall instead of step? Since the other timeouts are associated with specific statuses
rdeepak2002
approved these changes
Sep 19, 2026
rdeepak2002
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the clear pr description and tests! Left one optional suggestion
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.
Pull Request type
./gradlew build --write-locksto refresh dependencies)NOTE: Please remember to run
./gradlew spotlessApplyto fix any format violations.Changes in this PR
A step can now set a separate timeout for each phase of its life:
Today a step has one
timeout, measured from its start time. A step stuck waiting for a signal or a permit is never timed out, and there is no way to bound the whole step end to end. Withtimeouts, a step can be bounded in each phase independently, and a step that times out says which phase fired in its timeline:Step instance is timed out in phase [WAITING_FOR_SIGNALS] after [4h].The existing
timeoutfield is unchanged and keeps its meaning. A step sets eithertimeoutortimeouts, not both; the validator rejects a definition with both. Steps with neither behave exactly as today: only the running clock is bounded, at the 10 day default.Defaults are server configuration instead of constants.
maestro.step-timeouttakes a default for each phase and adefault-timeout-phasethat says which phase the singletimeoutfield applies to. This repo ships with the running default at 10 days anddefault-timeout-phase: running, which is today's behavior. A deployment that wants the singletimeoutto bound the whole step, or wants every step bounded while waiting for signals, sets that in its yaml.Step instances expose
timeouts_in_millisnext totimeout_in_millis, so clients can see the resolved limits. Steps already running when this is deployed carry onlytimeout_in_millisand keep being checked against the running clock.