Repository navigation
Train on rented GPUs with your coding agent, without losing checkpoints or paying for idle machines.
v1.2.1 is a patch release. It closes three ways a rented node could steer the local pull into writing outside its target, lets the pull run on the Bash 3.2 that macOS ships, and corrects four statements that could cost a run or money. No files were added, removed or renamed.
Pull safety
The rented node writes everything in a pulled tree, links and PULL_MANIFEST.json included, so nothing it sends may steer a local write outside the target.
scripts/verify_local.pywrotePULL_VERIFIED.jsonthrough the fixed temporary namePULL_VERIFIED.json.tmp. A link planted at that name redirected the write to any file the operator can write.tempfile.mkstempnow creates a fresh file that never follows a link (CodeQL alert #13).scripts/download_loop.shaccepted.and..as result directories, so..synced into the parent ofLOCAL_TARGET. Both are now refused, and local operands are passed as./NAMEso that a name such as-nis not read as an option.- Links the node can plant.
download_loop.shdeletes a manifest or.incomingcopy left by an earlier pull instead of writing through it, refuses a manifest that arrives as a link or not as a regular file, and does not sync a result directory that is a link inside the target. - Bash 3.2.
download_loop.shusedmapfile, which Bash 3.2 lacks, so under the/bin/bashthat macOS ships the pull stopped before syncing anything. A read loop replaces it.
Corrections
- vast.ai (
profiles/vastai.md): verify withvastai show instance INSTANCE_ID, using thenew_contractvalue thatcreate instanceprints. The offer ID is a different number. - AutoDL (
profiles/autodl.md): 关机 (shutdown) is a safe park for up to 15 days. The GPU meter stops but the data disk still bills a little, and an instance left off longer is released automatically with its data disk deleted. The profile's danger note already said this; the shutdown paragraph now agrees with it. - Fail-closed scope (
SKILL.md): the rule that a gate may fail closed only when passing it would make a reported number wrong now applies to research-protocol gates only. Data, secret and spend guards stay closed. - Rehearsal losses (
SKILL.md): the CPU rehearsal asserts finite losses, and non-negative ones only where the objective cannot go below zero. v1.2.0 asked for non-negative losses everywhere.
Upgrading
From v1.2.0, run the Install or update block in the README; it fast-forwards an existing clone. A setup that relied on a linked result directory needs one change: if a result directory inside LOCAL_TARGET is a link to another disk, the pull now reports it as FAIL and exits non-zero. Point LOCAL_TARGET at that disk instead.
Verification
On the release commit 566669c: python3 evals/run_evals.py → 49/49 cases reachable; python3 scripts/test_reconcile.py → 5 tests OK; the evals workflow and CodeQL code scanning passed; a gitleaks 8.30.1 scan of the full history found no leaks. Five regression tests for the pull fixes (a planted temporary link; ., .. and -n as result directories; a link left at either manifest name; a manifest served as a link; a result directory that is a link) pass under Bash 5.3 and under the Bash 3.2.57 that macOS ships, run against the released bytes of both scripts. They are kept outside this repository, so CI here does not run them. The two provider corrections come from a documentation audit, not from new runs on rented nodes.
Full changelog: v1.2.0...v1.2.1