Repository navigation
Reject invalid schedule time on deploy - #65
Merged
Merged
Conversation
JohanLorenzo
force-pushed
the
schedule-time-validation
branch
2 times, most recently
from
October 9, 2026 09:29
3b7ea28 to
b23f386
Compare
JohanLorenzo
force-pushed
the
schedule-time-validation
branch
from
October 9, 2026 09:30
b23f386 to
76be0f4
Compare
JohanLorenzo
marked this pull request as ready for review
October 9, 2026 09:40
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.
deploynow rejects anyschedule.timethat isn'tHH:MMbefore it sends a request. The error names the file and the bad value.stmo-cli writes
timeunquoted, so12:00is valid YAML 1.1 only as a sexagesimal number.Quoting on write is not an option here: serde_yaml does not quote individual fields, so the validation runs on deploy instead.
Evidence, run in a temporary directory against a dead local port:
time: 720exits 1 withschedule time '720' is not HH:MM, without connecting.time: '12:00'passes validation and fails only at the connection step.