record(ENV-LEASE-RUNTIME-STAGING): the leased worker compiles, downloads and runs Python, and AGENTS.md said it could do none of the three - #1215
Merged
Conversation
…ns Python, and three records said it could do none of the three (#1213) `AGENTS.md` told every agent that "the leased worker ... has no compiler, no downloader and no Python, so it cannot produce a runtime in place". `.agents/environment.md` carried the matching clause twice for `dgx:gpu0`. All three negatives are false, and the last clause is the consequential one. The clause is the stated basis for treating the pinned vLLM oracle as unreachable from a lease, and that oracle is the denominator for every speed-parity number the project owes. A reader who inherits it plans staging around a wall that is not there, and reaches for `ssh` instead, which is the bypass the lease rule exists to remove. `rc describe dgx:gpu0` prints an operator usage sheet. Under "What you get inside a job" it states that `rc run` executes the command in a container on the host, as root, with the GPU attached, that the container is Ubuntu 24.04, and that it carries `git`, `curl`, `wget`, `ssh`, `gcc`, `g++`, `make`, `cmake`, `ninja`, `pkg-config`, `python3`, `pip` and `venv`. It then instructs "Anything missing, install it - you are root", with `apt-get install` and `python3 -m venv` as its two examples. It names one real limitation, the absent CUDA toolkit. Two jobs then compiled inside a lease on 2026-08-18, so this is not read from a sheet alone. `claude/mudler-ubuntu-box/qwen38-gate` ran `/workspace/qwen38-gate/build.sh`, which apt-installed `cuda-nvcc-13-0`, `cuda-cudart-dev-13-0`, `libcublas-dev-13-0` and `cuda-crt-13-0` from the `ubuntu2404/sbsa` lane after `curl`ing NVIDIA's keyring, configured with `-DVLLM_CPP_CUDA=ON -DVLLM_CPP_CUDA_ARCHITECTURES=121a` against a host-staged CUTLASS v4.5.0, and built 1791 of 1791 targets to `BUILD_RC=0` and `BUILD_OK`. Its configure log is durable at `/mnt/nas_share/rc/qwen38-gate/out-main/cfg.log` and records `/usr/local/cuda-13.0/bin/nvcc`, `NVIDIA 13.0.88`, and `CUDA feature cutlass-fp8: ENABLED for [121a]`. Independently, `/mnt/nas_share/rc/mtp_test/build.sh` cloned `https://github.com/mudler/llama.cpp` from inside a job, and left a 97,101,264 byte `libggml-cuda.so` on the share, so downloader access is not a one-off. The correction does not flip into the opposite overstatement, and each part of that is deliberate. The HOST `dgx.casa` still has no egress to `github.com`, which is why `build.sh` stages CUTLASS host-side, while the CONTAINER reached `developer.download.nvidia.com` and `github.com`, so both records now name the side they mean. No CUDA toolkit is preinstalled, so a job installs `nvcc` per run. A global install leaks into the next job until the pod restarts, so project dependencies belong in a virtual environment under `/workspace`. `/workspace` is CIFS and holds no symlink, so a build happens in container-local `/tmp` and is copied out with `cp -rL`. Unconstrained parallelism has OOM-rebooted this box, so `-j 4`. **This claims nothing about the oracle, because nobody has tried.** #1185 already measured that the pinned oracle builds, installs and imports inside a lease on `dgx:gpu0`, and that a model run stays untested. This change claims only what is measured: a CUDA build of THIS tree completed inside a lease, so the premise behind the remaining blocker needs re-testing rather than inheriting. The re-test is recommended in #1213 and is not performed here. The 2026-08-17 probe readings stay in `.agents/environment.md` with their date and job ID, marked SUPERSEDED rather than deleted. That probe was taken correctly and the worker image changed under it, which is the same shape as #1146, and a reader has to be able to tell a stale reading from a wrong one. Records and documents only. `git diff 1f4878f -- src/ include/ tests/` is 0 lines. Gate, on `1f4878fdc97a06e6a21d15f856e8fd437d8634ea`: ```sh scripts/agent-preflight.sh --staged ``` `1 gate(s) failed: test_cpu_x86_llamacpp_floor`, rc=1. That harness test is untouched by this change and reds under box load; it reported `waiting for quiet: 15s busy=111% builders=0 load=107.93` while another session's build held the box. Every other gate is `ok`, including `check-agent-record`, `test_agent_record`, `check-issue-index append-only`, `test_gpu_lock_one_truth`, `check-env-doc`, `doc-checkpoint --staged` and `now-current --staged`. Closes nothing. #1213 stays open until the oracle premise is re-tested. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:claude-opus-5-1m [claude-code]
The leased worker on dgx:gpu0 compiles, downloads and runs Python, and AGENTS.md said it could do none of the three (#1213). Corrects the claim and marks the two matching clauses in environment.md as superseded. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Claude:Opus-5 [Claude Code]
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
2 participants
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.
AGENTS.mdsaid the leased worker "has no compiler, no downloader and no Python,so it cannot produce a runtime in place". On
dgx:gpu0it has all three and itdoes produce runtimes in place.
The device's own usage sheet lists the container as Ubuntu 24.04 running as root
with git, curl, wget, gcc, g++, make, cmake, ninja, python3, pip and venv, and
tells you to install anything missing. On 2026-08-18 a job did exactly that: it
apt-installed the CUDA compiler from NVIDIA's sbsa lane and configured this tree
at
sm_121aagainst a host-staged CUTLASS, with the configure log recordingCUDA feature cutlass-fp8: ENABLED for [121a]. A second, independent job in thesame period clones from github.com and curls NVIDIA's repo from inside a job, and
its output directory carries the full-size copies that
cp -rLleaves behind.This is not a wording quibble. The clause is the stated basis for treating the
pinned vLLM oracle as unreachable from a lease, and that oracle is the
denominator for every speed-parity number the project owes. Nobody has yet built
the oracle in a lease, and this change does not claim otherwise; it records that
the premise no longer holds and that the question is worth probing rather than
inheriting.
Four limits are real and are stated instead: no CUDA toolkit is preinstalled, a
global install leaks into the next job,
/workspaceis CIFS and holds nosymlink, and unconstrained parallelism has OOM-rebooted the box. The host and the
container also sit in different network positions, so the text now names which
side it means rather than saying "dgx has no egress".
.agents/environment.mdcarried the same claim in two clauses and is markedsuperseded in place, with the original probe reading and its date preserved. That
file was internally contradictory: one section said the worker cannot compile
while a later one recorded a lease building the pinned oracle from source.
The section's structure, its lease-over-ssh rule and its two-mutexes warning are
untouched.
Refs #1213, #1146.
FOLLOWING_AGENTS_PROTOCOL
Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: Claude:Opus-5 [Claude Code]