8000 fix(mctx,minimald,minvmd): a task on a VM-backed host_ip box runs in the classifier leaf of its box by minimal-foundry[bot] · Pull Request #3610 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

fix(mctx,minimald,minvmd): a task on a VM-backed host_ip box runs in the classifier leaf of its box - #3610

Merged
mitodrummer merged 12 commits into
mainfrom
agent/3582-a-task-on-a-vm-backed-host-ip-box-runs-in-the-cl
Nov 19, 2026
Merged

mitodrummer merged 12 commits into
mainfrom
agent/3582-a-task-on-a-vm-backed-host-ip-box-runs-in-the-cl

Conversation

@minimal-foundry
@minimal-foundry minimal-foundry Bot commented Nov 19, 2026 •
Copy link
Copy Markdown
Contributor

Follow-up

Fixes #3582

Task marker
### D3574 — A task on a VM-backed host_ip box runs in the classifier leaf of its box and gets the egress of its box
  kind: task
  size: M
  est: 140 code, 160 tests
  executor: agent
  origin: bug
  epic: 1437
  layers:
    - placement:
      - crates/mctx/src/env.rs: The task sandbox config gets with_classifier_leaf from the context leaf, so the task invocations join the leaf of the box
      - crates/mctx/src/lib.rs: make_env_with_network carries the context classifier leaf into the env args. Add a test that a leaf-bearing context gives a leaf-bearing task env
      - crates/minimald/src/env.rs: run_task keeps the classifier leaf of the box on the context it uses for run_invocations_relayed, and logs the leaf that the task runs in
      - crates/minimald/src/exec/process.rs: task_network gives a host_ip task the verdict of its box leaf, not the no-leaf plan
      - crates/minimald/src/net/provider.rs: task_network_for builds the HostIpAddressNetwork of a task with the box verdict and decision
      - crates/minimald/src/net/classifier.rs: Add a helper that gives the existing box leaf for a task of a host-address box, and update the NET-079 note that a task places no leaf
      test: cargo test -p mctx task_env_carries_the_box_classifier_leaf
      test: cargo test -p minimald run_task_runs_in_the_box_classifier_leaf
    - gate:
      - crates/minvmd/src/net/egress_gate.rs: Log the first dropped opening packet of each box once, with the source, the destination and the port, for node-plane and host_ip drops
      test: cargo test -p minvmd node_plane_drop_is_logged_once_per_box
    - cache:
      - crates/op/src/cache_clean.rs: An entry with no recorded read is stale only when its write time is before the cutoff
      test: cargo test -p op clean_keeps_an_unread_entry_written_after_the_cutoff
  proof: On macOS with host_ip, a task that opens /dev/tcp/www.google.com/443 and /dev/tcp/1.1.1.1/443 connects, the same as min box exec in that box.

Proof

A task of a host_ip box now runs in the classifier leaf of its box. This applies to an in-box min task run and to a task run over the exec channel. The task sandbox joins that leaf, so on a VM host the guest filter decides the task connections with the box verdict, the same as for min box exec.

macOS VM run

  • Host: Apple M5 Max, macOS 27.2.1 (arm64)
  • Commit: 7a65a15d (this PR's head)
  • Provider: local-minvmd (libkrun microVM), every box --network host_ip
  • Binaries: min, minvmd and bep built from this head by just minimal-cli minvmd-build (codesign last). The guest minimald is from just initramfs on this head; its initramfs carries this branch's new running an in-box task in the box's classifier leaf line. The VM ran from a private state dir (min --minimal-dir), so no existing box or daemon was involved. The minvmd log reports service.version 0.8.0-dev.632.g7a65a15d. The cross-built guest reports plain 0.8.0, because the container build has no git describe, so the run set MINIMAL_ALLOW_VERSION_SKEW=1.

The probe is the scratch project's task probe:

[tasks.probe]
bash = """
exec 3<>/dev/tcp/www.google.com/443 && echo google ok; exec 4<>/dev/tcp/1.1.1.1/443 && echo cf ok
"""
leg command exit output tail
setup min session activate -n p3610 --network host_ip . 0 box 01a1f45d-b454-79bf-ad82-5153efb72311
control min box exec p3610 -- bash -c 'exec 3<>/dev/tcp/www.google.com/443 && echo google ok; exec 4<>/dev/tcp/1.1.1.1/443 && echo cf ok' 0 google ok / cf ok
1: exec channel, from the host min task run --network host_ip probe 0 Running task probe in box probe-1... / google ok / cf ok / Kept box probe-1. ...
2: in-box, in the activated session min box exec p3610 -- min task run probe 0 google ok / cf ok

Guest minimald log for leg 1 (task box probe-1, 01a1f45e-0003-7577-8106-0991e1f229c4):

minimald::box_runtime::enforcement: the host-address box's egress verdict is decided on its classifier leaf, in the allow subtree session="probe-1" classifier="allow" leaf=/sys/fs/cgroup/minimald.slice/boxes/allow/01a1f45e-0003-7577-8106-0991e1f229c4 host_ip_enforcement=per_box
minimald::exec::process: task box: the run relays the box's entrypoint drop_env=0 start_dir=None stdin=true
minimald::env: running an in-box task in the box's classifier leaf box_name=probe-1 task=probe leaf=/sys/fs/cgroup/minimald.slice/boxes/allow/01a1f45e-0003-7577-8106-0991e1f229c4
sandbox: sandbox launch: box joins its classifier leaf before its cgroup namespace is unshared onto it leaf=/sys/fs/cgroup/minimald.slice/boxes/allow/01a1f45e-0003-7577-8106-0991e1f229c4
minimald::env: relaying a task's exit code to the in-box min helper task=probe exit_code=0
minimald::exec::process: task run: returned the entrypoint's exit code box_id=01a1f45e-0003-7577-8106-0991e1f229c4 box_name=probe-1 task=probe exit_code=Some(0)

Guest minimald log for leg 2 (session p3610, 01a1f45d-b454-79bf-ad82-5153efb72311):

minimald::box_runtime::enforcement: the host-address box's egress verdict is decided on its classifier leaf, in the allow subtree session="p3610" classifier="allow" leaf=/sys/fs/cgroup/minimald.slice/boxes/allow/01a1f45d-b454-79bf-ad82-5153efb72311 host_ip_enforcement=per_box
minimald::env: running an in-box task in the box's classifier leaf box_name=p3610 task=probe leaf=/sys/fs/cgroup/minimald.slice/boxes/allow/01a1f45d-b454-79bf-ad82-5153efb72311
sandbox: sandbox launch: box joins its classifier leaf before its cgroup namespace is unshared onto it leaf=/sys/fs/cgroup/minimald.slice/boxes/allow/01a1f45d-b454-79bf-ad82-5153efb72311
minimald::env: relaying a task's exit code to the in-box min helper task=probe exit_code=0

In the minvmd log, each box is held as a host_ip box (holding the host_ip box's egress rules ... resident_host_ip_boxes 1, then 2). The log has no dropped the first opening packet line for either box.

Notes from the agent: Touched outside the layers: crates/minimald/src/rpc/tests.rs. The test clean_cache_streams_progress_then_a_terminal_done wrote two unread entries just now and expected a 1s clean to delete them. That contradicts the new cache rule, so the test now writes them with a write time one hour back. Two tests inside the cache layer file needed the same kind of change: deletes_only_unused_unkept_entries now keeps the just-written unread entry, and reports_deletions_as_events records an old read for its entry. Design choices: (1) task_network keeps its signature, because exec/tests.rs and box_actor/setup.rs call it and are outside the layers. A new task_network_in_box_leaf takes the box leaf. run_task and the exec-channel task path call it. (2) task_network_for takes the box verdict and a decision. The callers pass decision None, because the box launch does not keep its Decision anywhere a task can read it. A Decision::decided() with no carve-out would make a native deny-all task refuse on the stale carve-out check. The verdict comes from the leaf (deny or allow subtree). On a VM host the plan does not depend on the verdict, so the leaf placement is the part of the fix that matters there. (3) classifier.rs had no literal 'a task places no leaf' note. That note was in provider.rs and process.rs, and both are updated. classifier.rs gets the task_box_leaf helper wi…[truncated]

Tests

line exit tail
cargo test -p mctx task_env_carries_the_box_classifier_leaf 0 running 1 test test tests::task_env_carries_the_box_classifier_leaf ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 77 filtered out; finished in 0.00s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runtime-implement-test-1: net
cargo test -p minimald run_task_runs_in_the_box_classifier_leaf 0 running 1 test test env::tests::run_task_runs_in_the_box_classifier_leaf ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1507 filtered out; finished in 0.38s running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 13 filtered out; finished in 0.00s runni
cargo test -p minvmd node_plane_drop_is_logged_once_per_box 0
cargo test -p op clean_keeps_an_unread_entry_written_after_the_cutoff 0 running 1 test test cache_clean::tests::clean_keeps_an_unread_entry_written_after_the_cutoff ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 59 filtered out; finished in 0.01s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runt

Verify

min task run agent-verify timed out after 1800s, so this PR is a draft.

nch\u{1f}PATH=/tmp/.tmpV62N3X/replybin:/usr/bin:/bin:/usr/sbin:/sbin:/home/.local/bin\u{1f}PWD=/tmp/.tmpV62N3X/some dir\u{1f}RUSTC_WRAPPER=sccache\u{1f}SCCACHE_BUCKET=agent-runtime-sccache-gominimal-minimal\u{1f}SCCACHE_ENDPOINT=https://4103a6df4dd77276970745a22603bea9.r2.cloudflarestorage.com\u{1f}SCCACHE_REGION=auto\u{1f}SCCACHE_S3_USE_SSL=true\u{1f}SHELL=/usr/bin/bash\u{1f}SHLVL=2\u{1f}SSL_CERT_DIR=/etc/ssl/certs\u{1f}SSL_CERT_FILE=/etc/ssl/cert.pem\u{1f}XDG_CACHE_HOME=/state/cache\u{1f}XDG_CONFIG_HOME=/home/.config\u{1f}XDG_DATA_HOME=/home/.local/share\u{1f}XDG_RUNTIME_DIR=/run\u{1f}XDG_STATE_HOME=/home/.local/state\u{1e}stdin\n"
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

  Cancelling due to test failure: 3 tests still running
        PASS [   0.329s] ( 705/2436) minimald env::tests::task_entrypoint_relays_the_task_exit_code
        PASS [   3.459s] ( 706/2436) minimald env::tests::run_task_relays_exit_through_both_paths
        SLOW [> 60.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>120.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>180.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>240.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>300.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>360.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>420.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>480.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>540.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>600.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>660.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>720.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>780.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>840.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>900.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>960.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1020.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1080.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1140.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1200.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1260.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task

Base

The base branch moved while the coder worked; it was merged in before the tests ran.

Out of scope

These files are outside the task's layers:, so this PR is a draft:

  • crates/minimald/src/rpc/tests.rs

A context made for a host-address box carries the leaf of that box.
The task env args now take it, so the task sandbox joins the leaf and
the box egress verdict decides the task connections.
A task of a host-address box ran with no leaf. On a VM host the guest
filter then dropped its connections, while the same connection from
min box exec passed. run_task keeps the box leaf on its context and logs
it, and the task network follows the verdict of that leaf.
A node-plane or host_ip drop line is rate limited, so it can name a
later frame or an ACK in place of the packet that opened the flow. The
gate now logs the first dropped opening packet of each source once,
with the source, the destination and the port.
An entry with no recorded read was stale at once, so a clean could
delete a package written moments before. It is now stale only when its
write time is before the cutoff. The minimald clean RPC test writes
its cold entries an hour back to match.
@coderabbitai
coderabbitai Bot commented Nov 19, 2026 •
8000 Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

Ask an organization administrator to verify that this bot has an active assigned CodeRabbit review seat. See the seat-assignment guide. After the seat is confirmed, request a review again.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 62860c1b-b163-4eab-a893-5e35a45cd702

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

An unread cache entry now stays when its write time is after the
cutoff. The maintenance tests wrote their cold entries with the current
time, so a clean kept them. Write them twice UNUSED_FOR ago.
@minimal-foundry
Copy link
Copy Markdown
Contributor Author

Round 1 of 10 on a failed check suite, pushed as 8539c8fe8355.

line exit tail
cargo test -p mctx task_env_carries_the_box_classifier_leaf 0 running 1 test test tests::task_env_carries_the_box_classifier_leaf ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 79 filtered out; finished in 0.00s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runtime-implement-test-1: net
cargo test -p minimald run_task_runs_in_the_box_classifier_leaf 0 running 1 test test env::tests::run_task_runs_in_the_box_classifier_leaf ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1514 filtered out; finished in 0.57s running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 13 filtered out; finished in 0.00s runni
cargo test -p minvmd node_plane_drop_is_logged_once_per_box 0
cargo test -p op clean_keeps_an_unread_entry_written_after_the_cutoff 0 running 1 test test cache_clean::tests::clean_keeps_an_unread_entry_written_after_the_cutoff ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 59 filtered out; finished in 0.00s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runt

Verify min task run agent-verify timed out after 1800s.

nch\u{1f}PATH=/tmp/.tmpOu5H2E/replybin:/usr/bin:/bin:/usr/sbin:/sbin:/home/.local/bin\u{1f}PWD=/tmp/.tmpOu5H2E/some dir\u{1f}RUSTC_WRAPPER=sccache\u{1f}SCCACHE_BUCKET=agent-runtime-sccache-gominimal-minimal\u{1f}SCCACHE_ENDPOINT=https://4103a6df4dd77276970745a22603bea9.r2.cloudflarestorage.com\u{1f}SCCACHE_REGION=auto\u{1f}SCCACHE_S3_USE_SSL=true\u{1f}SHELL=/usr/bin/bash\u{1f}SHLVL=2\u{1f}SSL_CERT_DIR=/etc/ssl/certs\u{1f}SSL_CERT_FILE=/etc/ssl/cert.pem\u{1f}XDG_CACHE_HOME=/state/cache\u{1f}XDG_CONFIG_HOME=/home/.config\u{1f}XDG_DATA_HOME=/home/.local/share\u{1f}XDG_RUNTIME_DIR=/run\u{1f}XDG_STATE_HOME=/home/.local/state\u{1e}stdin\n"
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

  Cancelling due to test failure: 3 tests still running
        PASS [   0.385s] ( 714/2445) minimald env::tests::task_entrypoint_relays_the_task_exit_code
        PASS [   4.105s] ( 715/2445) minimald env::tests::run_task_relays_exit_through_both_paths
        SLOW [> 60.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>120.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>180.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>240.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>300.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>360.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>420.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>480.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>540.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>600.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>660.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>720.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>780.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>840.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>900.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>960.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1020.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1080.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1140.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1200.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1260.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task

Outside the task's layers::

  • crates/minimald/src/maintenance.rs
  • crates/minimald/src/rpc/tests.rs

Converted to a draft: something above needs a person before review.

On macOS with host_ip, a task in a box runs in the classifier leaf of that box and gets the same egress verdict. A task that opens /dev/tcp/www.google.com/443 and /dev/tcp/1.1.1.1/443 connects, the same as min box exec in that box. This round also makes the Linux test lane pass again: the minimald maintenance tests now agree with the new cache-clean rule.

Notes from the agent: The CI log excerpt did not name the failing test. I found it locally: three minimald maintenance::tests (clean_runs_with_no_sessions, clean_keeps_what_a_session_needs_and_drops_the_rest, concurrent_requests_are_serialized) failed. The cause is the op cache_clean change in this task. An unread entry now stays when it is written after the cutoff, and these tests wrote their 'cold' entries with the current time. The fix gives the test helper write_entry a write time of 2 * UNUSED_FOR ago. crates/minimald/src/maintenance.rs is outside the task's layers. I changed it only in its test module because the layer's behavior change requires it. crates/minimald/src/rpc/tests.rs is also outside the layers. An earlier round changed it for the same reason. Local environment issues that do not come from this branch: (1) MINIMAL_OTEL=off in this box makes env::tests::task_entrypoint_carries_env_cwd_and_args fail and two stdin tests hang, so I ran minimald tests with MINIMAL_OTEL unset. (2) rustdoc is missing here, so mctx doctests did not run. (3) Some net::switch, box_actor, connection and answerer tests fail in a full parallel run but pass when run alone. Those modules are unchanged on this branch. A full cargo test -p minimald --lib did not finish inside 30 minutes, so I ran the affected modules one by one. The proof needs a macOS host_ip VM run (just e2e), and this box cannot run it.

@minimal-foundry
Copy link
Copy Markdown
Contributor Author

Round 2 of 10 on a failed check suite: the coder changed nothing. Revise round 2: I changed nothing. The directive gives two failed checks. ci-linux-kvm-success is only the aggregator of test-kvm. The test-kvm excerpt holds only the source lines of the workflow scripts that contain '::error::', and setup lines. It does not show the step that failed or its output. So I cannot tell which harness failed, or if the cause is this branch or a flake. This box has no /dev/kvm, so I cannot run 'just test-vm', the lifecycle script or scripts/session-e2e.sh. I read the branch diff against the KVM paths. Only host-address boxes get a classifier leaf (box_actor/setup.rs says an own-address box has none), so own_ip tasks keep their earlier sandbox and network. The new gate line is a WARN, and the e2e script says WARN drop lines pass either way. I found no e2e proof that the change breaks. All four test: lines pass at the merged head 807bebac. Next step: someone with access must read the full test-kvm log (run 44445651300, job 135300067912), find the fa…[truncated]

@norrietaylor
norrietaylor marked this pull request as ready for review November 19, 2026 06:38
@norrietaylor
norrietaylor requested a review from a team as a code owner November 19, 2026 06:38
@norrietaylor
Copy link
Copy Markdown
Member

Un-drafted: the failed job passed on a re-run of the same head (a timing flake in a test this diff does not touch), and every lane is now green.

@norrietaylor
Copy link
Copy Markdown
Member

/review

@norrietaylor
Copy link
Copy Markdown
Member

/arch-review

@minimal-foundry
minimal-foundry Bot commented Nov 19, 2026 •
Copy link
Copy Markdown
Contributor Author

Reviewed: 1 finding, none blocking at 8dcc5698a05b.

Address the comments on the diff.

Clobber: none seen.

@minimal-foundry minimal-foundry Bot left a comment
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minimal-review — advisory review

Verdict COMMENT — 2 findings, 2 inline.

Panel: 3 of 3 personas ran (correctness, security, supply-chain).

Comment thread crates/minimald/src/exec/process.rs Resolved
@minimal-arch minimal-arch Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arch-review: CONDITIONS · 2 conditions · the full ruling

The task placement conforms. A host_ip task now joins its box's classifier leaf, as §4.1 and the min box exec contract require. The new minvmd drop line does not record what it claims. It latches on the source address. On both rules that address is shared, by minimald or by the whole host_ip cohort. §4.1 says per-box attribution in the cohort is impossible. Fix the message, the doc comments and the marker text in C1. Run the macOS proof leg and record it, as C2 says.

Ruled at 8539c8f against gominimal/arch@8b824707cde6 by claude-opus-5-5.

Comment thread crates/minvmd/src/net/egress_gate.rs Resolved
Comment thread crates/minvmd/src/net/egress_gate.rs Resolved
Comment thread crates/minimald/src/env.rs Resolved
@minimal-arch minimal-arch Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arch-review: PASS_WITH_CONDITIONS · 1 condition · the full ruling

The change conforms to the design. A task of a host_ip box now runs in the classifier leaf of its box. So its connections take the cohort address and not the node-plane address, as deployment-and-egress-gateway.md §4.1 line 54 requires. The gate log line and the cache-clean rule are design-silent. The task's own proof is not run: the PR body says no macOS VM run was made. C1 asks for that run on macOS with host_ip, for both task paths, and its result in the ## Proof section.

Ruled at 8539c8f against gominimal/arch@8b824707cde6 by claude-opus-5-5.

Comment thread crates/minimald/src/exec/process.rs Resolved
Comment thread crates/minimald/src/env.rs Resolved
@norrietaylor norrietaylor left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I traced both task paths, the in-box run_task and the exec-channel task_producer. Each carries the box leaf into the task env: Context::task_env_args passes it to place_in_classifier_leaf, and the sandbox pre-exec join puts the task in the leaf. task_network_in_box_leaf builds the same HostIpAddressNetwork plan that the box launch builds. The None decision matches what tasks passed before, so this is not a regression. I found no correctness bug. The cache_clean write-time rule is sound: an entry whose meta is missing or unreadable still counts as old. The test updates in maintenance.rs and rpc/tests.rs match the new rule. The minenv_run_forwards_stdin_to_the_task hang in the Verify section uses a stub channel and does not reach the code changed here. One low note is inline, about test coverage of the wiring. The existing architect threads are still open and need answers before merge: the FirstOpeningDrops doc and message say "box", but the latch keys on (rule, node source address), and the macOS host_ip proof run is still owed.


Generated by Claude Code

Comment thread crates/minimald/src/env.rs Resolved
A task of a native deny-all host_ip box joins its box leaf. Its plan now
carries a decided decision with the carve-out the leaf's tree records, so
a task started after the answerer moved or stopped is refused, the same
as the box launch, and never falls back to the constant answerer.
@norrietaylor
Copy link
Copy Markdown
Member

The macOS host_ip proof the arch review asks for (C2, and the two C1 proof notes) is tracked in 3639 as #3639; the runtime's coder cannot run a macOS VM.

@minimal-foundry
Copy link
Copy Markdown
Contributor Author

Round 3 of 10 on the runtime's review findings, pushed as 7a65a15d43b0.

line exit tail
cargo test -p mctx task_env_carries_the_box_classifier_leaf 0 running 1 test test tests::task_env_carries_the_box_classifier_leaf ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 79 filtered out; finished in 0.00s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runtime-implement-test-1: net
cargo test -p minimald run_task_runs_in_the_box_classifier_leaf 0 running 1 test test env::tests::run_task_runs_in_the_box_classifier_leaf ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1515 filtered out; finished in 0.31s running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 13 filtered out; finished in 0.00s runni
cargo test -p minvmd node_plane_drop_is_logged_once_per_box 0
cargo test -p op clean_keeps_an_unread_entry_written_after_the_cutoff 0 running 1 test test cache_clean::tests::clean_keeps_an_unread_entry_written_after_the_cutoff ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 60 filtered out; finished in 0.00s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runt

Verify min task run agent-verify timed out after 1800s.

e-sccache-gominimal-minimal\u{1f}SCCACHE_ENDPOINT=https://4103a6df4dd77276970745a22603bea9.r2.cloudflarestorage.com\u{1f}SCCACHE_REGION=auto\u{1f}SCCACHE_S3_USE_SSL=true\u{1f}SHELL=/usr/bin/bash\u{1f}SHLVL=2\u{1f}SSL_CERT_DIR=/etc/ssl/certs\u{1f}SSL_CERT_FILE=/etc/ssl/cert.pem\u{1f}XDG_CACHE_HOME=/state/cache\u{1f}XDG_CONFIG_HOME=/home/.config\u{1f}XDG_DATA_HOME=/home/.local/share\u{1f}XDG_RUNTIME_DIR=/run\u{1f}XDG_STATE_HOME=/home/.local/state\u{1e}stdin\n"
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

  Cancelling due to test failure: 3 tests still running
        PASS [   0.308s] ( 712/2447) minimald env::tests::search_finds_known_package
        PASS [   2.739s] ( 713/2447) minimald env::tests::run_task_relays_exit_through_both_paths
        SLOW [> 60.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>120.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>180.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>240.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>300.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>360.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>420.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>480.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>540.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>600.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>660.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>720.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>780.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>840.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>900.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>960.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1020.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1080.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1140.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1200.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1260.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1320.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1380.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task

Outside the task's layers::

  • crates/minimald/src/maintenance.rs
  • crates/minimald/src/rpc/tests.rs

Converted to a draft: something above needs a person before review.

Review threads the coder judged:

  • 👍 valid — crates/minimald/src/exec/process.rs: A task in a deny leaf now plans over the decision from classifier::task_box_decision. It carries the carve-out that the leaf's tree records, so a stale or missing answerer refuses the task, the same as the launch. A new test pins it: task_in_a_deny_leaf_refuses_a_stale_carve_out.

A task started in a host_ip box runs in the classifier leaf of that box and gets the same egress as min box exec in that box. On macOS with host_ip, a task that opens /dev/tcp/www.google.com/443 and /dev/tcp/1.1.1.1/443 connects. On a native deny-all host_ip box, a task started after the DNS answerer moved or stopped is refused, the same as the box launch.

Notes from the agent: Revise round 3. The review thread is valid. The fix adds classifier::task_box_decision: a native deny leaf of a running box exists only when its launch decided per box, so the task plans over a decided decision with the carve-out that the leaf's tree records now. The task does not run the table probe again. That probe binds a listener and forks a child, so it is too heavy for each task run. The macOS proof needs a VM host, and this box did not run it. cargo clippy -p minimald --all-targets and cargo fmt --check are clean.

@minimal-foundry
minimal-foundry Bot marked this pull request as draft November 19, 2026 07:27
@minimal-arch minimal-arch Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arch-review: PASS_WITH_CONDITIONS · 1 condition · the full ruling

The code conforms to §4.1 line 54. A task of a host_ip box now runs in its box's classifier leaf, and a deny-leaf task repeats the stale carve-out check. That check fails closed. C1 stays open. The PR body still says that no macOS VM end-to-end run was made. On a VM host, §7.1 line 245 puts the split in the VM's netfilter, so only that run proves the fix. Run the task proof on macOS for both task paths. Then record the command, the exit code and the output tail in ## Proof.

Ruled at 7a65a15 against gominimal/arch@8b824707cde6 by claude-opus-5-5.

Comment thread crates/minimald/src/env.rs Resolved
Comment thread crates/minimald/src/exec/process.rs Resolved
@norrietaylor
Copy link
Copy Markdown
Member

/arch-review

@minimal-arch minimal-arch Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arch-review: PASS_WITH_CONDITIONS · 1 condition · the full ruling

The task placement fix conforms to §4.1. A task of a host_ip box now joins its box's leaf and gets the box's verdict, and a deny leaf fails closed on a stale carve-out. The new first-opening drop line in egress_gate.rs claims a per-box record that the gate cannot make. Section 4.1 says per-box attribution in the cohort is impossible, and node-plane drops are minimald's own traffic. Make the edit in C1, so the line says it is once per rule and source address. The verify run is still open: it timed out with a test failure that this review cannot name.

Ruled at 7a65a15 against gominimal/arch@8b824707cde6 by claude-opus-5-5.

10BC8
Comment thread crates/minvmd/src/net/egress_gate.rs Resolved
Comment thread crates/minvmd/src/net/egress_gate.rs Resolved
Comment thread crates/minvmd/src/net/egress_gate.rs Resolved
@norrietaylor
Copy link
Copy Markdown
Member

/revise Apply arch condition C1 at 7a65a15 exactly as ruled (crates/minvmd/src/net/egress_gate.rs, FirstOpeningDrops):

  • C1: crates/minvmd/src/net/egress_gate.rs FirstOpeningDrops: state what the latch is keyed by, and do not claim a box. (1) Rewrite the doc comment so that it says one line per rule and source address on this relay. Remove "the source address on one relay names the box the drop is for". (2) Change the tracing::warn! message to "dropped the first opening packet leaving the VM under this rule from this source address; later drops under this rule from this source are only in the rate-limited drop line". Keep the fields source, destination, port, rule_matched. (3) Rename the test node_plane_drop_is_logged_once_per_box to first_opening_drop_is_logged_once_per_rule_and_source. Make it assert that a second HOST_IP_BOXES_RULE opening from the same node address, as a second host_ip box sends it, writes no line.

Also from the three C1 threads: rename the test at line ~8563 that uses two node addresses as two boxes, and assert that a second opening under HOST_IP_BOXES_RULE from the same node address writes no line. Keep the four log fields. Change nothing else; the macOS proof in the PR body stands.

The source address on a relay does not name a box: every host_ip box and
the node plane leave from the node address. Say so in the doc comment and
the log line, and rename the test to match.
@minimal-foundry
Copy link
Copy Markdown
Contributor Author

Round 4 of 10 on a /revise note, pushed as 8dcc5698a05b.

line exit tail
cargo test -p mctx task_env_carries_the_box_classifier_leaf 0 ud-gax-internal v0.7.20 Compiling uuid v1.28.0 Compiling miette v7.6.0 Compiling num-bigint v0.4.8 Compiling rayon v1.12.0 Compiling nickel-lang-core v0.19.0 Compiling google-cloud-longrunning v1.14.0 Compiling jaq-json v2.0.2 Compiling topiary-core v0.7.3 Compiling tempfi
cargo test -p minimald run_task_runs_in_the_box_classifier_leaf 0 loud-lro v1.11.0 Compiling version v0.8.0 (/workbench/crates/version) Compiling google-cloud-storage v1.20.0 Compiling stdlib v0.0.22 (/workbench/crates/stdlib) Compiling pathrs v0.2.5 Compiling fd-lock v4.0.4 Compiling nix v0.30.1 Compiling netlink-packet-route v0.25.1 Compi
cargo test -p minvmd node_plane_drop_is_logged_once_per_box 0
cargo test -p op clean_keeps_an_unread_entry_written_after_the_cutoff 0 running 1 test test cache_clean::tests::clean_keeps_an_unread_entry_written_after_the_cutoff ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 60 filtered out; finished in 0.00s warning: unknown fields in task runtime-implement-test-0: network warning: unknown fields in task runt

Verify min task run agent-verify timed out after 1800s.

er_flushes_last_line_on_shutdown
        PASS [   0.011s] ( 717/2458) minimald env::tests::subject_hash_matches_openssl
        PASS [   0.011s] ( 718/2458) minimald env::tests::task_entrypoint_drops_ignored_vars
  stdout ───

    running 1 test
    test env::tests::task_entrypoint_carries_env_cwd_and_args ... FAILED

    failures:

    failures:
        env::tests::task_entrypoint_carries_env_cwd_and_args

    test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 1521 filtered out; finished in 0.02s

  stderr ───

  Cancelling due to test failure: 3 tests still running
        PASS [   0.260s] ( 720/2458) minimald env::tests::task_entrypoint_relays_the_task_exit_code
        PASS [   3.233s] ( 721/2458) minimald env::tests::run_task_relays_exit_through_both_paths
        SLOW [> 60.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>120.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>180.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>240.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>300.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>360.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>420.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>480.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>540.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>600.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>660.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>720.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>780.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>840.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>900.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>960.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1020.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1080.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1140.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1200.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1260.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1320.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task
        SLOW [>1380.000s] (─────────) minimald env::tests::minenv_run_forwards_stdin_to_the_task

The coder's box did not compile these files. Check them in CI: crates/mctx/src/env.rs, crates/mctx/src/lib.rs, crates/minimald/src/env.rs, crates/minimald/src/exec/process.rs, crates/minimald/src/maintenance.rs, crates/minimald/src/net/classifier.rs, crates/minimald/src/net/provider.rs, crates/minimald/src/rpc/tests.rs, crates/op/src/cache_clean.rs.

Outside the task's layers::

  • crates/minimald/src/maintenance.rs
  • crates/minimald/src/rpc/tests.rs

Converted to a draft: something above needs a person before review.

Review threads the coder judged:

  • 👍 valid — crates/minvmd/src/net/egress_gate.rs: Rewrote the FirstOpeningDrops doc comment: one line per rule and source address on this relay. Removed the claim that the source names the box.
  • 👍 valid — crates/minvmd/src/net/egress_gate.rs: The warn message is now the C1 text, with no mention of a box. The four fields source, destination, port and rule_matched stay.
  • 👍 valid — crates/minvmd/src/net/egress_gate.rs: Renamed the test to first_opening_drop_is_logged_once_per_rule_and_source and removed the second node address. It asserts that a second HOST_IP_BOXES_RULE opening from the same node address writes no line.

On macOS with host_ip, a task that opens /dev/tcp/www.google.com/443 and /dev/tcp/1.1.1.1/443 connects, the same as min box exec in that box. This round changes only the minvmd drop log: it now says one line per rule and source address, and it does not claim a box.

Notes from the agent: Revise round 4 applies arch condition C1 only. The doc comment of FirstOpeningDrops and of its note method now say that the latch is one line per rule and source address on this relay. The warn message is the C1 text, with the fields source, destination, port and rule_matched. The test node_plane_drop_is_logged_once_per_box is renamed to first_opening_drop_is_logged_once_per_rule_and_source. It no longer uses a second node address as a second box. It asserts that a second HOST_IP_BOXES_RULE opening from the same node address writes no line. The task.md test line still names the old test, so cargo test -p minvmd node_plane_drop_is_logged_once_per_box now matches no test. Run the new name in its place. Clippy and rustfmt for minvmd are clean. No other layer changed this round.

@norrietaylor
norrietaylor marked this pull request as ready for review November 19, 2026 19:38
@norrietaylor
Copy link
Copy Markdown
Member

Marked ready: the round pushed and every lane aggregator is green at 8dcc569; the draft came from the round's verify step, not from a failing lane.

@norrietaylor
Copy link
Copy Markdown
Member

/review

@norrietaylor
Copy link
Copy Markdown
Member

/arch-review

@minimal-foundry minimal-foundry Bot left a comment
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minimal-review — advisory review

Verdict COMMENT — 1 finding, 1 inline.

Panel: 3 of 3 personas ran (correctness, security, supply-chain).

Comment on lines 128 to +134
let stale: Vec<SpecHash> = cache
.iter_entries()
.filter(|hash| !self.keep.contains(hash))
.filter(|hash| atimes.last_read(hash).is_none_or(|last| last < cutoff))
.filter(|hash| match atimes.last_read(hash) {
Some(last) => last < cutoff,
None => written_before(cache, hash, cutoff),
})
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOW · correctness · confidence 0.55 · in CleanCache::run

This hunk changes how CleanCache treats never-read entries. An unread entry now stays until its write time passes the cutoff. Before, it was always stale. This does not trace to the PR goal of running a task in its box leaf. It also changes what min cache clean removes for every user. Move it to its own PR, or state the reason in the PR body.

What the reviewer checked

cache_clean.rs:131 None => written_before(cache, hash, cutoff), (was: is_none_or(|last| last < cutoff))

Hand this to an agent
Act on a code-review finding.

File:       crates/op/src/cache_clean.rs
Lines:      128-134
Category:   correctness
Severity:   low (reviewer confidence 0.55)

Finding:
This hunk changes how `CleanCache` treats never-read entries. An unread entry now stays until its write time passes the cutoff. Before, it was always stale. This does not trace to the PR goal of running a task in its box leaf. It also changes what `min` cache clean removes for every user. Move it to its own PR, or state the reason in the PR body.

First verify this against the code yourself. It is model output and
may be wrong. If it is wrong, or the tradeoff was deliberate, say so
and change nothing.

👍 useful · 👎 noise — react to tell the reviewer. Replying works too, and says more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disputed — not addressed: This change is in scope. The task's cache layer names crates/op/src/cache_clean.rs: "An entry with no recorded read is stale only when its write time is before the cutoff". The test line clean_keeps_an_unread_entry_written_after_the_cutoff pins it. Before this change, a clean could delete an entry that was written moments earlier and not read yet.

@minimal-arch minimal-arch Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

arch-review: PASS · the full ruling

C1 is met at this head. The FirstOpeningDrops doc and log line now say one line per rule and source address, and they do not claim a box. This agrees with §4.1 line 54, which says per-box attribution in the host_ip cohort is impossible. The renamed test asserts that a second host_ip opening from the node address writes no line. The merges of main do not touch the task leaf placement or the cache rule, so the earlier status stands. Update the task marker test name to first_opening_drop_is_logged_once_per_rule_and_source when you run the proof again.

Ruled at 8dcc569 against gominimal/arch@8b824707cde6 by claude-opus-5-5.

@minimal-foundry
Copy link
Copy Markdown
Contributor Author

Round 5 of 10 on the runtime's review findings: the coder changed nothing. every commit this round put on the branch above 8dcc569 is a merge of the base branch, so it carries no work of its own

Review threads the coder judged:

  • 👎 invalid — crates/op/src/cache_clean.rs:134: This change is in scope. The task's cache layer names crates/op/src/cache_clean.rs: "An entry with no recorded read is stale only when its write time is before the cutoff". The test line clean_keeps_an_unread_entry_written_after_the_cutoff pins it. Before this change, a clean could delete an entry

@norrietaylor
Copy link
Copy Markdown
Member

/revise
One review finding at 8dcc569 (crates/op/src/cache_clean.rs, CleanCache::run, lines 128–134, from commit cb2a272 "fix(op): keep an unread cache entry written after the cutoff"): this changes what a cache clean removes for every user and does not trace to this PR's goal (a task runs in its box leaf). PR #3501 makes the same change on its own branch.

Revert cb2a272's changes to crates/op/src/cache_clean.rs and crates/minimald/src/rpc/tests.rs, so this branch leaves the cache clean as main has it. Then run cargo test -p op and cargo test -p minimald rpc::tests (and this PR's own test lines). If a test of this PR fails without the change, keep the change instead, and say in your round reply which test fails and why, so the PR body can give the reason.

@minimal-foundry
Copy link
Copy Markdown
Contributor Author

That /revise is held, not dropped. The container platform had no instance to give the coder: its pool of prepared containers was full, which happens most just after a deploy. Your note is kept and asked again every 10 minutes for up to 30; a wait that outlives that is refused here with the reason.

What the platform said

could not start the coder: Error: there is no container instance that can be provided to this durable object

Nothing to type again: the command gets a rocket when its round starts, or a refusal that names the reason. No round was counted for it yet.

@mitodrummer mitodrummer left a comment
Copy link
Copy Markdown
EF81
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

D3574 — A task on a VM-backed host_ip box runs in the classifier leaf of its box and gets the egress of its box

2 participants

0