🔻 going-down message + downtime in success post#19
Open
amiller wants to merge 1 commit into
Open
Conversation
Two adds in one PR — they're both about closing the visibility gap
between the heads-up and the success message:
1. New step "going-down notice" runs immediately before phala deploy.
Posts a "🔻 restarting CVM now — back in ~2 min" message to
ADMIN_COMMAND_ROOM and records DOWNTIME_START_TS in $GITHUB_ENV.
The cancel window has closed by this point.
2. Health check captures DOWNTIME_END_TS the moment /versions starts
returning 200 again. Post-deploy note now reads both timestamps and
includes "downtime: ~Xs" in the body, e.g.
🚀 deployed abc1234 to dstack-matrix
downtime: ~95s
<commit message>
run: ...
Each deploy now produces three messages in #matrix-devops:
- 🚧 deploying X in ~10 min — cancel: <link>
- 🔻 restarting CVM now — back in ~2 min ← new
- 🚀 deployed X — downtime: ~Xs ← downtime field new
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Two visibility adds for the deploy flow, both in one PR since they're tightly related:
1. New step: "going-down notice"
Runs immediately before
phala deploy(i.e. after the 10-min countdown). Posts toADMIN_COMMAND_ROOM:Why: the heads-up post says "in 10 min" but there's no signal at the moment the actual restart fires. Anyone watching #matrix-devops who reads the heads-up but then forgets — they'd see SSL handshake failures on mtrx without knowing why. The 🔻 message removes the gap. Also sets
DOWNTIME_START_TSin$GITHUB_ENV.2. Downtime field in success post
Health check step now also writes
DOWNTIME_END_TSto$GITHUB_ENVthe moment/versionsreturns 200 again. Post-deploy note reads both timestamps:So now you can eyeball deploy-to-deploy whether Phala is being slow ("90s downtime, normal") vs hitting trouble ("420s downtime, getting close to the recovery branch").
Three messages per deploy now
Each carries distinct info: heads-up + cancel window / outage starts now / outage ended + how long.
Will land in v0.5 whenever you tag it.