[earakely-scale]

Summary

A deploy whose required setting doesn't resolve (an env: or secret: reference with no value here) recorded the build as failing at the probe: "it didn't boot: Unresolved env:… reference". Nothing had been booted, and later deploys then refused the build (DeployRefused … 'failed') until it was rebuilt with env build.

The cause: _probe resolves the boot settings before booting, and checked treated every exception as a failed boot.

Now:

• _probe raises Unprobed when a setting doesn't resolve (ConfigError), booting nothing.
• checked leaves the build unverified, with the reason "not probed: a setting it boots with didn't resolve here: …".
• A later run, bundle register or env build probes it once the setting resolves.

A deploy that doesn't compose (env deploy, a stored task's run) now composes such a container again first, when its provider runs it natively. It reuses the image, probes it, and deploys it only once ready. A deploy whose setting still doesn't resolve is refused with that container's reason. Disks and VM bundles are unchanged: their first boot probes them.

Test plan

• New unit test, using the real _probe with an app secret token = "env:MAIL_TOKEN". Without the variable the build is unverified, with that reason, and pending. With it set, a compose reaches ready from the same image. It fails on main ('failed' != 'unverified').

• Follow-up (bebb0174), two new tests that fail on the first commit:

  • a deploy probes a container left unverified once its setting resolves, and boots it only once ready;
  • a deploy refuses a container still unverified for a setting that doesn't resolve, giving the reason.

  test_a_computer_env_with_no_ready_build_is_refused… is unchanged and passes. Unit tier: 13755 passed, with the same 3 host-specific failures as main.

• test_computer_env.py (70 selected) passes.

• On an arm64 Linux host, follow-up: a deploy without the variable is refused with the reason; then agent-env env deploy with it set probes the same image (unverified → ready) and deploys.

• On an arm64 Linux host: the run without the variable now records unverified: not probed …. With it set, the build is reused, becomes ready in 17 s, and the task deploys.

• ruff check is clean.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; the latest change fixes the hidden refusal reason without excluding usable builds.

Summary

Missing boot settings now leave builds unverified rather than failed. Later deploys can reuse and probe the image.

• Computer builds stay unverified when a boot setting cannot be resolved.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Build or reuse image] --> B[Resolve boot settings]
  B -->|Missing value| C[Leave build unverified with reason]
  C --> D[Later compose or deploy retries]
  D --> B
  B -->|Settings resolve| E[Boot and probe]
  E -->|Pass| F[Mark ready]
  E -->|Fail| G[Mark failed]
  F --> H[Deploy on a supported provider]

Loading

_{Reviews (8) · Last reviewed commit: "fix(computer): say why a native containe..." · Reviewed by Greptile}