From c8f3b7ae0f04e3b0783236cc00e8afd97134d54a Mon Sep 17 00:00:00 2001 From: garrytan Date: Mon, 2 Nov 2026 18:17:21 +0000 Subject: [PATCH] docs(pregate): the run key hashes the runner script and setup, not a gstack version Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/pregate.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pregate.md b/docs/pregate.md index 70667b328..c7a232508 100644 --- a/docs/pregate.md +++ b/docs/pregate.md @@ -618,8 +618,8 @@ A run killed before its teardown line leaves its VM running. A machine restart kills a background pregate this way. Don't destroy the VM first: rerun the same `gstack-pregate` command before anything it depends on changes. The run key covers the tree, the planned file set, the commit `origin/HEAD` points at (a -`git fetch` that moves it counts), `UBI_LOCATION`, the size, the environment -and the gstack version. When the rerun prints `reattaching to VM ` with +`git fetch` that moves it counts), `UBI_LOCATION`, the size, the environment, +and the runner script and setup it uploads. When the rerun prints `reattaching to VM ` with the name from the create line, it finishes the run on that VM and bills from the VM's original create. When it creates a new VM instead (the key changed, or the restart came before the runner recorded the VM), destroy the old one