Approved by the owner on 2026-10-22. Procedure: change `channel`, run `rustup show`, then run the pipeline. What changed - rust-toolchain.toml and eoc/eoc-rs/rust-toolchain.toml: channel "1.98.0" becomes "1.99.1". These are the only two pins in the tree, and the root one governs every other cargo root. - 64 workflows under .github/workflows (the forge's CI): every `Install Rust 1.98.0`, `rustup toolchain install / default / component add / target add --toolchain 1.98.0` and `--default-toolchain 1.98.0` now names 1.99.1 (409 lines). Two of those lines are in build steps rather than install steps (wai-conformance.yml's two `wasm32 (unix)` steps each `rustup target add --toolchain`), and they move with the rest: a target added to a toolchain that is not installed is an error. - Left as they are, because they record what was measured on 1.98.0: standards-build.yml's "Verified on a native arm64 Linux container (rustc 1.98.0)", wai-conformance.yml's note on Rust 1.98's LLD 22, and the "rustc 1.98.0 (example)" strings in receipts, vectors and docs. The one-codegen-unit workaround that note explains also stays. 1.99.1 ships LLD 23.1.1, which the note says links those inputs, but removing the workaround should wait for a run at the CI path on x86_64. Why - 1.98.0 has a P-critical miscompile, rust-lang/rust#161441 (I-miscompile, regression-from-stable-to-stable). rustc emits a vacant (null) method slot in a trait-object vtable, so a safe dynamic call jumps to address zero (undefined behaviour). RELEASES.md records the fix in 1.98.1 ("rustc: fix miscompilation in generating vtables"). - 1.99.1 is the current stable (channel manifest dated 2026-10-15; rustc 58cf8f9c3 2026-10-13). It also fixes 1.99.0's own regressions: wcslen on UEFI and embedded targets, x86_64 FFI `bool` returns, and the rust-lld rpath on macOS. Evidence All of it ran on the build host ([email protected], aarch64-apple-darwin) through ~/kani-logs/remote/rb. Nothing was built on the dev Mac. - `rustup show`: the active toolchain is 1.99.1-aarch64-apple-darwin, "overridden by .../rust-toolchain.toml" (and by eoc/eoc-rs's own file there). rustc 1.99.1 (58cf8f9c3 2026-10-13), LLVM 23.1.1, clippy 0.1.99, rustfmt 1.10.0. The baseline is rustc 1.98.0 (88d9e12ae 2026-08-18). - Scope: every cargo root the pin governs, which is 46 of the 49 tracked lockfiles. The other three: two are vendored crates that resolve inside their parents, and wai/wai-rs/fuzz builds on its own pinned nightly. - Trees. The final tree is main at96117c570plus these two commits. Main moved four times while this ran, and each root's evidence comes from the newest tree it was run on: - 13 roots on the final tree: every root main changed after1a465f23d, and every root that consumes such a crate by path. - 12 roots on1a465f23dplus these two commits. - 7 roots onb16816671plus these two commits. - 14 roots onaa61ab3b9plus the pin change. For each root in the last three groups, checked with git diff and the lockfiles' path packages: none of its files, and no crate it reaches by path, differs on the final tree. - Each root got: (a) `cargo fmt --all -- --check` on the pin and on 1.98.0. The output is byte-identical in all 46. CI gates no root on rustfmt, and none is rustfmt-clean on main. (b) `cargo clippy --locked --keep-going --workspace --all-targets` on both toolchains, with the diagnostics compared line by line. After the previous commit, no root has a diagnostic that only 1.99.1 reports. openpay's one differing line is the same lint at the same site, reworded. (c) `cargo test --workspace --locked`. (d) the root's other CI steps that can run on this host: feature-gated tests, conformance suites, release-profile tests, the aac page-set checks, and every clippy -D warnings gate. The gates are standards-build's macOS meter and omni lints (jouleclaw-energy x2, jouleclaw-omni metal, jouleclaw-loader-gguf, jcp, proof, eoc, sandbox), wai-pack, wai-quantum-cli (default, no-default and metal), wai-quantum-service, wai-quantum-qpu and wai-quantum-desktop. - Totals: `cargo test --workspace` ran in 43 roots: 12,532 passed, 1 failed, 101 ignored. The other 3 roots are wasm32-only, and their `cargo build --release --target wasm32-unknown-unknown` passed. Every other CI step passed (62 of 62). - On the final tree: scripts/check-lockfiles.sh (cargo 1.99.1) found all 47 lockfiles current, and scripts/check-advisories.py passes. - tokio is 1.54.1 in every lockfile cargo reads. That is patched for both RUSTSEC-2026-0386 (>= 1.53.3) and RUSTSEC-2026-0384 (>= 1.54.1). The 1.53.1 in vendor/wtransport/Cargo.lock is the upstream file kept with the vendored source; cargo resolves wtransport inside its parents, and both gates skip that file. - What is not green, each one reproduced on 1.98.0: - wai-ops-gpu: under the debug profile, `corpus` trips the debug_assert at exec.rs:187 on both toolchains. CI runs it in release only, and that passes (6/6). - wai-ops: clippy::derived_hash_with_manual_eq (deny-by-default) on both toolchains. No CI job runs clippy there. - wai-vector/wasm: `--all-targets` cannot build the lib-test target (its own `panic_impl`) on either toolchain. `clippy --lib` for wasm32 reports 0 diagnostics on both. - eoc-cascade's hit_calibration_process_energy test reads real energy counters, and it fails some of the time on the loaded shared host. In interleaved runs each toolchain passed 18 of 20. The full eoc-rs suite passed on the final tree (741 passed). - Environment, not code: - wai-quantum-desktop embeds the Studio's build, so wai/quantum-studio was built first (`npm ci`, `node build.mjs`), as CI does. - Not covered here: the x86_64 and arm64 Linux and Windows legs; the GPU, NPU, FPGA, emulator and hardware-meter legs; wasm32 tests under Node, wasmtime and wasip2; and the fuzz job. Co-Authored-By: Claude Opus 5.5 <[email protected]>
296 lines
14 KiB
YAML
296 lines
14 KiB
YAML
name: WAI HTTP delivery
|
||
|
||
# extensions/http-delivery.md: the falsification, the differential and the cache rules,
|
||
# beside the corpus checks in wai-conformance.yml.
|
||
#
|
||
# falsify — the HTTP corpus tool and its independent verifier must catch defects. Each
|
||
# patch in wai/http-conformance/falsify/ breaks one function of wai-rs (the content
|
||
# hash's domain, the root flag, the left-subtree rule, the chunk counter, the component
|
||
# digest check, the Content-Range and content-coding checks, ASCII-only numbers, the
|
||
# union, layers' place in it and their dispatch, the wai prefix's case, duplicate
|
||
# capabilities, a record beside a fallback, the trailing-byte rule, the missing-digest
|
||
# plan, the class merge, the base-only threshold, refused refinement responses, stale
|
||
# bytes after a mismatch, an unanswered base, the selection digest test, the component
|
||
# conformance that withholds an envelope's refinements; and on the
|
||
# playlist side adjacency, rendering, bandwidths, durations, the classical master, the
|
||
# playlist receipt and its chain, listed cids, and the adaptation policies; and on the
|
||
# receipt side the receipt file's name, legacy groups, the parent walk and its bound,
|
||
# the caps on files, indexes and their items, fetching each name once within budgets
|
||
# of files and bytes, what a client holds of an object, the items a claim attaches
|
||
# through, §3.1 step 6 for every class and the declarations it reads by name, the
|
||
# ancestor rule, its recovery and the publisher key it uses, a claim's parent,
|
||
# anchoring from the origin only and the request that anchors, cached logs, grants
|
||
# files and sets held by their pins); it
|
||
# is applied to one worktree of the head, built once and rebuilt incrementally per
|
||
# patch under the `falsify` profile (overflow checks and debug assertions on, as in the
|
||
# tests), and `wai_http_vectors verify` must fail naming the cases on the patch's first
|
||
# line; the patch is then reversed and the tree must be clean. Each `http_verify.py
|
||
# --mutate` must exit non-zero naming the cases falsify/mutations.txt lists for it; a
|
||
# crash, or a non-zero exit that names none, is a failure. Both run in shards (falsify/run.sh --patches I/N, --mutations
|
||
# I/N), each printing what it ran and failing unless that is exactly what was assigned
|
||
# to it; `shards` checks the shards the matrix declares cover every patch and every
|
||
# mutation once, so none is dropped silently.
|
||
#
|
||
# differential — the corpus verified both ways, and the differential: wai-rs writes
|
||
# random envelopes' covered prefixes and head proofs, the Python verifier accepts every
|
||
# one, and refuses exactly the ten it changes one chaining-value byte in.
|
||
#
|
||
# cache-conformance — the cache rules (§9). wai/cache-conformance/run.sh stages the
|
||
# corpus's objects behind the reference origin (`wai http origin`) and runs driver.py
|
||
# against the origin, which must pass every MUST test, and against four negative-control
|
||
# proxies, which must each fail the tests their defect reaches. Labelled caches run only
|
||
# where the environment provides them (/opt/wai-cache); this repository holds none, and
|
||
# the job summary says when none ran. The reports are uploaded as an artifact.
|
||
#
|
||
# No workflow_dispatch: it does not start runs on this forge. A weekly schedule keeps the
|
||
# jobs exercised between changes.
|
||
|
||
concurrency:
|
||
group: ${{ github.workflow }}-${{ github.ref }}
|
||
cancel-in-progress: true
|
||
|
||
on:
|
||
pull_request:
|
||
paths:
|
||
- 'wai/wai-rs/src/http_binding/**'
|
||
- 'wai/wai-rs/src/container.rs'
|
||
- 'wai/wai-rs/src/jwp_hash.rs'
|
||
- 'wai/wai-rs/src/bin/wai.rs'
|
||
- 'wai/wai-rs/src/bin/wai_http_vectors.rs'
|
||
- 'wai/wai-rs/src/bin/wai_cli/http.rs'
|
||
- 'wai/wai-rs/src/bin/wai_cli/http_vectors.rs'
|
||
- 'wai/wai-rs/src/bin/wai_cli/http_vectors_playlists.rs'
|
||
- 'wai/wai-rs/src/bin/wai_cli/http_vectors_receipts.rs'
|
||
- 'wai/wai-rs/src/bin/wai_cli/http_playlists.rs'
|
||
# Receipts, keys, grants and sets over HTTP (§8.1–§8.5) are checked by the receipt,
|
||
# claim, key-log and pin code, and on the Python side by their own verifiers.
|
||
- 'wai/wai-rs/src/jwp_delivery.rs'
|
||
- 'wai/wai-rs/src/claim_receipt.rs'
|
||
- 'wai/wai-rs/src/claim_receipt/**'
|
||
- 'wai/wai-rs/src/key_log.rs'
|
||
- 'wai/wai-rs/src/pin.rs'
|
||
# ...and by what those read with: JCS, signer identities, step 6's figures and
|
||
# classes, and the OER receipts an energy claim names.
|
||
- 'wai/wai-rs/src/jcs.rs'
|
||
- 'wai/wai-rs/src/signer_id.rs'
|
||
- 'wai/wai-rs/src/energy_class.rs'
|
||
- 'wai/wai-rs/src/energy_figure.rs'
|
||
- 'wai/wai-rs/src/energy_binding.rs'
|
||
- 'wai/wai-rs/src/energy_report.rs'
|
||
- 'wai/wai-rs/src/claim_text.rs'
|
||
- 'wai/wai-rs/src/oer.rs'
|
||
- 'wai/jwp-conformance/jwp_verify.py'
|
||
- 'wai/claim-conformance/claim_verify.py'
|
||
- 'wai/signer-conformance/signer_verify.py'
|
||
- 'wai/oer-conformance/oer2_verify.py'
|
||
# The playlists render through hls_render and are sealed by wai_video_manifest.
|
||
- 'wai/wai-rs/src/hls_render.rs'
|
||
- 'wai/wai-rs/src/wai_video_manifest.rs'
|
||
# Playlist receipts verify Ed25519 through the shared strict rule, in Rust and Python.
|
||
- 'wai/wai-rs/src/sig.rs'
|
||
- 'wai/claim-conformance/_ed25519.py'
|
||
- 'wai/http-conformance/**'
|
||
- 'wai/cache-conformance/**'
|
||
- 'wai/claim-conformance/_blake3.py'
|
||
# http_verify.py reads staged_verify.py (and through it int_payload_verify.py), and
|
||
# the corpus carries the staged ladder's base and layers.
|
||
- 'wai/staged-conformance/staged_verify.py'
|
||
# staged_verify.py's component rules (SPEC §7.1) read the capability registry.
|
||
- 'wai/staged-conformance/cases/audio_flac_rate_ladder/**'
|
||
- 'wai/int-payload-conformance/int_payload_verify.py'
|
||
- '.github/workflows/wai-http.yml'
|
||
schedule:
|
||
- cron: '17 4 * * *'
|
||
|
||
jobs:
|
||
# The path filters above gate the trigger, which on this forge is the push delta: a
|
||
# rebase fires them all. This gates the work, from the pull request's own diff, reading
|
||
# the path list out of this file (scripts/pr-touches-paths.py); a push to main or the
|
||
# schedule has no pull-request context and runs everything.
|
||
relevant:
|
||
name: WAI HTTP · does this change touch it
|
||
runs-on: linux
|
||
outputs:
|
||
run: ${{ steps.gate.outputs.run }}
|
||
falsify: ${{ steps.gate.outputs.falsify }}
|
||
steps:
|
||
- uses: actions/checkout@v5
|
||
with:
|
||
fetch-depth: 0
|
||
- id: gate
|
||
run: |
|
||
set -euo pipefail
|
||
base="${{ github.event.pull_request.base.sha }}"
|
||
head="${{ github.event.pull_request.head.sha }}"
|
||
r=$(python3 scripts/pr-touches-paths.py .github/workflows/wai-http.yml "$base" "$head")
|
||
echo "this change touches WAI HTTP: $r"
|
||
echo "run=$r" >> "$GITHUB_OUTPUT"
|
||
# The falsify shards (about an hour and a half of runner time) prove that the corpus
|
||
# tool and its verifier catch defects: they matter when a pull request changes the
|
||
# code the patches in http-conformance/falsify/ break, the corpus, its verifier or
|
||
# this file. Any other change to the list above runs the corpus jobs but not the
|
||
# shards. The nightly schedule, having no pull request, runs them all. Fails open:
|
||
# a diff that cannot be read answers true.
|
||
f=true
|
||
if [ -n "$base" ] && [ -n "$head" ] && names=$(git diff --name-only "$base...$head"); then
|
||
if grep -qE '^(wai/wai-rs/src/http_binding/|wai/http-conformance/|wai/wai-rs/src/bin/wai_http_vectors\.rs$|wai/wai-rs/src/bin/wai_cli/http|wai/wai-rs/src/(container|sig|jwp_hash|jwp_delivery|hls_render|wai_video_manifest)\.rs$|\.github/workflows/wai-http\.yml$)' <<< "$names"; then
|
||
f=true
|
||
else
|
||
f=false
|
||
fi
|
||
fi
|
||
echo "this change touches what the falsify shards break: $f"
|
||
echo "falsify=$f" >> "$GITHUB_OUTPUT"
|
||
|
||
# Every patch and every mutation runs in exactly one shard: the one whose index mod N
|
||
# it is, in the sorted list. The shards job reads the list below; keep it on one line.
|
||
falsify:
|
||
name: HTTP corpus · falsify ${{ matrix.shard }}
|
||
needs: relevant
|
||
if: needs.relevant.outputs.falsify == 'true'
|
||
runs-on: linux-arm64
|
||
strategy:
|
||
fail-fast: false
|
||
matrix:
|
||
shard: ['patches 0/3', 'patches 1/3', 'patches 2/3', 'mutations 0/3', 'mutations 1/3', 'mutations 2/3']
|
||
steps:
|
||
- uses: actions/checkout@v5
|
||
|
||
- name: Install Rust 1.99.1
|
||
if: startsWith(matrix.shard, 'patches')
|
||
shell: bash
|
||
run: |
|
||
export PATH="$HOME/.cargo/bin:$PATH"
|
||
command -v rustup >/dev/null 2>&1 || \
|
||
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
|
||
rustup toolchain install 1.99.1 --profile minimal
|
||
rustup default 1.99.1
|
||
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
|
||
|
||
- uses: actions/setup-python@v5
|
||
with:
|
||
python-version: '3.11'
|
||
|
||
# http_verify.py checks the receipt and key cases through the corpora's receipt,
|
||
# claim and key-discovery verifiers, which check Ed25519's equation with this
|
||
# package; its mutations reach those cases.
|
||
- name: Install the Ed25519 library
|
||
shell: bash
|
||
run: python -m pip install cryptography
|
||
|
||
- name: Every patch or mutation of this shard is caught
|
||
shell: bash
|
||
env:
|
||
CARGO_TARGET_DIR: ${{ runner.temp }}/falsify-target
|
||
SHARD: ${{ matrix.shard }}
|
||
run: |
|
||
git config --global --add safe.directory "$GITHUB_WORKSPACE"
|
||
set -- $SHARD
|
||
bash wai/http-conformance/falsify/run.sh "$RUNNER_TEMP/falsify" "--$1" "$2"
|
||
|
||
# The shards the matrix above declares cover every patch and every mutation exactly
|
||
# once: a shard dropped from the list, or a total that disagrees, fails here.
|
||
shards:
|
||
name: HTTP corpus · every patch and mutation in exactly one shard
|
||
needs: relevant
|
||
if: needs.relevant.outputs.run == 'true'
|
||
runs-on: linux
|
||
steps:
|
||
- uses: actions/checkout@v5
|
||
- shell: bash
|
||
run: |
|
||
set -euo pipefail
|
||
line=$(grep -E "^ +shard: \[" .github/workflows/wai-http.yml)
|
||
mapfile -t shards < <(printf '%s\n' "$line" | grep -oE "'(patches|mutations) [0-9]+/[0-9]+'" | tr -d "'")
|
||
bash wai/http-conformance/falsify/run.sh "$RUNNER_TEMP/falsify" --check-shards "${shards[@]}"
|
||
|
||
differential:
|
||
name: HTTP corpus · verified both ways, and the differential
|
||
needs: relevant
|
||
if: needs.relevant.outputs.run == 'true'
|
||
runs-on: linux-arm64
|
||
steps:
|
||
- uses: actions/checkout@v5
|
||
|
||
- name: Install Rust 1.99.1
|
||
shell: bash
|
||
run: |
|
||
export PATH="$HOME/.cargo/bin:$PATH"
|
||
command -v rustup >/dev/null 2>&1 || \
|
||
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
|
||
rustup toolchain install 1.99.1 --profile minimal
|
||
rustup default 1.99.1
|
||
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
|
||
|
||
- uses: actions/setup-python@v5
|
||
with:
|
||
python-version: '3.11'
|
||
|
||
- name: Install the Ed25519 library
|
||
shell: bash
|
||
run: python -m pip install cryptography
|
||
|
||
- name: The corpus, both ways; the differential
|
||
shell: bash
|
||
env:
|
||
CARGO_TARGET_DIR: ${{ runner.temp }}/falsify-target
|
||
run: |
|
||
set -euo pipefail
|
||
git config --global --add safe.directory "$GITHUB_WORKSPACE"
|
||
(cd wai/wai-rs && cargo build --profile falsify --no-default-features --features http,video_manifest,key_discovery --bin wai_http_vectors)
|
||
"$CARGO_TARGET_DIR/falsify/wai_http_vectors" verify wai/http-conformance
|
||
(cd wai/http-conformance && python3 http_verify.py .)
|
||
bash wai/http-conformance/falsify/run.sh "$RUNNER_TEMP/falsify" --differential
|
||
|
||
cache-conformance:
|
||
name: cache rules · controls and labelled caches
|
||
needs: relevant
|
||
if: needs.relevant.outputs.run == 'true'
|
||
runs-on: linux-arm64
|
||
steps:
|
||
- uses: actions/checkout@v5
|
||
|
||
- name: Install Rust 1.99.1
|
||
shell: bash
|
||
run: |
|
||
export PATH="$HOME/.cargo/bin:$PATH"
|
||
command -v rustup >/dev/null 2>&1 || \
|
||
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.99.1
|
||
rustup toolchain install 1.99.1 --profile minimal
|
||
rustup default 1.99.1
|
||
echo "$HOME/.cargo/bin" >> "$GITHUB_PATH"
|
||
|
||
- uses: actions/setup-python@v5
|
||
with:
|
||
python-version: '3.11'
|
||
|
||
- name: Build the reference origin
|
||
working-directory: wai/wai-rs
|
||
shell: bash
|
||
run: cargo build --release --no-default-features --features http --bin wai
|
||
|
||
# The verdict: run.sh exits non-zero when the origin fails a MUST test, a control is
|
||
# not caught, or a labelled cache fails one.
|
||
- name: The origin passes, the controls are caught, labelled caches report
|
||
shell: bash
|
||
run: WAI="$GITHUB_WORKSPACE/wai/wai-rs/target/release/wai" bash wai/cache-conformance/run.sh "$RUNNER_TEMP/cache"
|
||
|
||
# The evidence in the log, whatever becomes of the upload: each report's path and
|
||
# SHA-256, and the summary.
|
||
- name: The reports, in the log
|
||
if: always()
|
||
shell: bash
|
||
run: |
|
||
cd "$RUNNER_TEMP/cache/reports" 2>/dev/null || { echo "no reports were written"; exit 0; }
|
||
for f in *; do printf '%s %s\n' "$(sha256sum "$f" | cut -d' ' -f1)" "$RUNNER_TEMP/cache/reports/$f"; done
|
||
cat summary.md 2>/dev/null || true
|
||
|
||
# An upload this forge cannot take must not decide the job: the verdict is the step
|
||
# above it.
|
||
- name: Upload the reports
|
||
if: always()
|
||
continue-on-error: true
|
||
uses: actions/upload-artifact@v3
|
||
with:
|
||
name: cache-conformance-reports
|
||
path: ${{ runner.temp }}/cache/reports
|