Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

Rust 1.98.0 -> 1.99.1: toolchain pin (change-controlled) and the lints clippy 1.99 adds #472

Closed
dcharlot wants to merge 2 commits from chore/rust-1.99.1 into main
pull from: chore/rust-1.99.1
merge into: Transaction-Science:main
Conversation 0 Commits 2 Files changed 63 +288 -265
dcharlot commented 2026-10-25 22:05:03 -04:00
Owner
Copy link

What this changes

This moves the toolchain pin from Rust 1.98.0 to 1.99.1 (the current stable). It is a change-controlled pin; the owner approved it on 2026-10-22. There are two commits:

  1. clippy 1.99: fix what Rust 1.99.1's clippy newly reports. These are the only diagnostics 1.99.1 reports that 1.98.0 did not, across every cargo root in the tree. 1.98.0's clippy also builds the fixed code and reports nothing new.
    • clippy::assert_is_empty (new in 1.99): 36 test-only sites in aac-core, access-core and eight openpay crates. assert!(x.is_empty()) becomes assert_eq!(x, [] as [T; 0]) (or assert_ne!, or "" for strings), so a failure prints the value. aac-core and access-core #![deny(clippy::all)], so their clippy run fails on 1.99.1 without this. Judgment call: clippy's own "MachineApplicable" suggestion does not compile at 18 of the 36 sites (it uses crate-relative paths that test modules cannot see, or a bare [] whose type cannot be inferred). Each site names its element type as its module sees it, and lines are wrapped as rustfmt wraps them.
    • clippy::approx_constant (deny-by-default) now knows EULER_GAMMA and GOLDEN_RATIO (stable since 1.94; the jouleclaw MSRV is 1.97).
      • jouleclaw-omni mochi.rs: 1.618_034 becomes f32::consts::GOLDEN_RATIO. They are the same f32 bits, so outputs do not change. This was failing standards-build's macOS gate clippy -p jouleclaw-omni --features metal -- -D warnings.
      • jouleclaw-outlier c_factor: 0.5772156649 becomes f64::consts::EULER_GAMMA. Judgment call: c(n) moves by 3.1e-12, because the literal was truncated and the isolation-forest paper's normalisation uses γ itself. Nothing else reads these scores.
    • smart-byte-rs Cargo.lock: async-trait 0.1.89 becomes 0.1.92 (with syn 3.0.9). 0.1.89 put #[must_use] on every method it generates, and clippy 1.99 now counts Pin<Box<dyn Future>> as must_use, so double_must_use fired at 9 trait methods. The attribute came from the macro, so the fix is the macro: 0.1.92, the version every other lockfile here already uses, no longer emits it. An incidental syn 2 to syn 1 move of data-encoding-macro-internal was put back, so the lock changes only what the bump needs.
  2. toolchain: Rust 1.98.0 to 1.99.1. This covers both pins (rust-toolchain.toml and eoc/eoc-rs/rust-toolchain.toml) and every 1.98.0 the workflows install (34 files, 224 lines). Lines that record a measurement made on 1.98.0 are left alone: the standards-build "Verified … (rustc 1.98.0)" note, wai-conformance's LLD 22 note and its one-codegen-unit workaround, and the rustc 1.98.0 (example) strings in receipts and vectors. 1.99.1 ships LLD 23.1.1, so that workaround could be dropped after one x86_64 run at the CI path.

Why

  • rust-lang/rust#161441 (P-critical, I-miscompile, regression-from-stable-to-stable): rustc 1.98.0 can emit a vacant (null) method slot in a trait-object vtable, so a safe dynamic call jumps to address zero. That is undefined behaviour in safe code. RELEASES.md records the fix in 1.98.1.
  • 1.99.1 is the current stable (channel manifest dated 2026-10-15). It also fixes 1.99.0's own regressions: x86_64 FFI bool returns, wcslen on UEFI and embedded targets, and the rust-lld rpath on macOS.

Evidence

Everything ran on the build host (aarch64-apple-darwin) through rb. rustup show reports 1.99.1 as active, overridden by rust-toolchain.toml (rustc 1.99.1 (58cf8f9c3 2026-10-13), LLVM 23.1.1). The baseline is rustc 1.98.0 (88d9e12ae 2026-08-18).

The scope is every cargo root the pin governs: 46 of the 49 tracked lockfiles. Two of the rest are vendored crates resolved inside their parents, and wai/wai-rs/fuzz uses its own pinned nightly. The final tree is main at 96117c570 plus these two commits. Main moved four times while this ran, so each root's row below names the newest tree it was run on. For each root in the older 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. The groups: 13 roots on the final tree, 12 on 1a465f23d, 7 on b16816671 (each with both commits), and 14 on aa61ab3b9 with the pin change. Each root got:

  • rustfmt: cargo fmt --all -- --check on the pin and on 1.98.0 gives byte-identical output in all 46. CI gates no root on rustfmt, and none is rustfmt-clean on main.
  • clippy: cargo clippy --locked --keep-going --workspace --all-targets ran on both toolchains, with the diagnostics compared line by line. After commit 1, 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.
  • tests: cargo test --workspace --locked, plus each root's other CI steps that run on macOS arm64: feature-gated tests, conformance suites, release-profile tests, the aac page-set checks, and every clippy -D warnings gate (standards-build's macOS meter and omni lints, wai-pack, wai-quantum-cli default/no-default/metal, wai-quantum-service, wai-quantum-qpu, wai-quantum-desktop).
  • scripts/check-lockfiles.sh with cargo 1.99.1: all 47 lockfiles are current. scripts/check-advisories.py passes on the final tree. tokio is 1.54.1 in every lockfile cargo reads, which is patched for both RUSTSEC-2026-0386 and RUSTSEC-2026-0384. 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.

Totals: cargo test --workspace ran in 43 roots (12,532 passed, 1 failed, 101 ignored). The 3 wasm32-only roots built for wasm32-unknown-unknown. The other CI steps passed (62 of 62).

Per root
root tree rustfmt: pin vs 1.98.0 clippy diagnostics: pin / 1.98.0 / only on pin cargo test --workspace: passed / failed / ignored other CI steps passing
arl/arl-rs aa61ab3b9 51 hunks, identical 13 / 13 / 0 58 / 0 / 0 –
sense/sense-rs aa61ab3b9 112 hunks, identical 0 / 0 / 0 45 / 0 / 0 –
joulehook/joulehook-rs b16816671 12925 hunks, identical 0 / 0 / 0 34 / 0 / 0 –
joule-ui/joule-ui-rs aa61ab3b9 2777 hunks, identical 2 / 2 / 0 72 / 0 / 0 –
pool/pool-rs aa61ab3b9 78 hunks, identical 0 / 0 / 0 74 / 0 / 0 –
smart-byte/smart-byte-rs 1a465f23d 642 hunks, identical 57 / 57 / 0 708 / 0 / 0 –
openpay 1a465f23d 452 hunks, identical 308 / 308 / 1 ² 1951 / 0 / 6 –
map/map-rs b16816671 248 hunks, identical 1 / 1 / 0 228 / 0 / 0 1/1
aac/aac-rs b16816671 3279 hunks, identical 2 / 2 / 0 711 / 0 / 5 3/3
aac/aac-rs/tools/symbols/bbox aa61ab3b9 3 hunks, identical 0 / 0 / 0 0 / 0 / 0 –
joulecontract/joulecontract-rs aa61ab3b9 3144 hunks, identical 2 / 2 / 0 84 / 0 / 0 –
proof/proof-rs aa61ab3b9 3097 hunks, identical 0 / 0 / 0 173 / 0 / 0 2/2
eoc/eoc-rs 1a465f23d 802 hunks, identical 33 / 33 / 0 741 / 0 / 3 2/2
eoc/eoc-bench b16816671 802 hunks, identical 0 / 0 / 0 15 / 0 / 0 –
jcp/jcp-rs b16816671 2650 hunks, identical 3 / 3 / 0 582 / 0 / 0 3/3
sandbox/sandbox-rs b16816671 2650 hunks, identical 0 / 0 / 0 440 / 0 / 0 3/3
mesh/mesh-rs 1a465f23d 12890 hunks, identical 43 / 43 / 0 106 / 0 / 0 1/1
jouledesk/jouledesk-rs 1a465f23d 12711 hunks, identical 0 / 0 / 0 44 / 0 / 1 –
joule-code/joule-code-rs 96117c570 7356 hunks, identical 19 / 19 / 0 571 / 0 / 1 7/7
joule-code/joule-code-rs/crates/joule-moq-room 96117c570 26052 hunks, identical 2 / 2 / 0 17 / 0 / 0 –
joule-code/examples/l3-jouleclaw 1a465f23d 17320 hunks, identical 45 / 45 / 0 15 / 0 / 5 –
joule-code/examples/transport-moqt 1a465f23d 7322 hunks, identical 0 / 0 / 0 2 / 0 / 0 –
jouleclaw/jouleclaw-rs 1a465f23d 12581 hunks, identical 417 / 417 / 0 5017 / 0 / 74 10/10
wai/byte-exact-conformance aa61ab3b9 1327 hunks, identical 37 / 37 / 0 101 / 0 / 0 1/1
wai/tools/ops-gpu-bench 1a465f23d 30896 hunks, identical 1 / 1 / 0 0 / 0 / 0 1/1
wai/tools/quantum-meter 96117c570 16808 hunks, identical 0 / 0 / 0 10 / 0 / 0 1/1
wai/tools/quantum-wgsl-check 96117c570 4218 hunks, identical 0 / 0 / 0 0 / 0 / 0 –
wai/wai-live-web 1a465f23d 18374 hunks, identical 1 / 1 / 0 7 / 0 / 0 1/1
wai/wai-ops aa61ab3b9 698 hunks, identical 41 / 41 / 0 ¹ 53 / 0 / 3 1/1
wai/wai-ops/node aa61ab3b9 699 hunks, identical 0 / 0 / 0 wasm32 build ok –
wai/wai-ops-gpu b16816671 829 hunks, identical 0 / 0 / 0 4 / 1 / 0 ³ 1/1
wai/wai-ops-gpu/browser aa61ab3b9 837 hunks, identical 0 / 0 / 0 wasm32 build ok –
wai/wai-pack 96117c570 18888 hunks, identical 1 / 1 / 0 70 / 0 / 0 3/3
wai/wai-quantum 96117c570 4172 hunks, identical 6 / 6 / 0 82 / 0 / 2 1/1
wai/wai-quantum-cli 96117c570 4366 hunks, identical 0 / 0 / 0 8 / 0 / 0 5/5
wai/wai-quantum-desktop 96117c570 4386 hunks, identical 0 / 0 / 0 4 / 0 / 0 2/2
wai/wai-quantum-qpu 96117c570 4311 hunks, identical 0 / 0 / 0 21 / 0 / 0 1/1
wai/wai-quantum-serve 96117c570 18344 hunks, identical 2 / 2 / 0 10 / 0 / 0 –
wai/wai-quantum-service 96117c570 4287 hunks, identical 0 / 0 / 0 23 / 0 / 0 2/2
wai/wai-relay 1a465f23d 18287 hunks, identical 1 / 1 / 0 0 / 0 / 0 –
wai/wai-spz-gen 1a465f23d 18294 hunks, identical 1 / 1 / 0 0 / 0 / 0 –
wai/wai-vector aa61ab3b9 594 hunks, identical 1 / 1 / 0 81 / 0 / 0 3/3
wai/wai-vector/wasm aa61ab3b9 603 hunks, identical 1 / 1 / 0 ¹ wasm32 build ok –
wai/wai-verify aa61ab3b9 1399 hunks, identical 5 / 5 / 0 36 / 0 / 0 1/1
wai/wai-web 96117c570 18677 hunks, identical 8 / 8 / 0 35 / 0 / 0 1/1
wai/wai-rs 96117c570 18315 hunks, identical 50 / 50 / 0 299 / 0 / 1 5/5

¹ clippy cannot finish on either toolchain: wai-ops has a deny-by-default derived_hash_with_manual_eq, and wai-vector/wasm's lib-test target clashes with its own panic_impl. For wai-vector/wasm, clippy --lib --target wasm32-unknown-unknown reports 0 diagnostics on both.
² This is the same lint at the same site (op-dispute-evidence evidence.rs:92), with its message reworded in 1.99.
³ This is a debug-profile debug_assert (exec.rs:187) on both toolchains. CI runs this crate in release only, and that passes (6/6).

Not green, and not from the toolchain (each reproduced on 1.98.0 or on main)

  • wai-ops-gpu: under the debug profile, corpus trips debug_assert!(i32::try_from(v).is_ok()) on both toolchains. CI's release-only run passes.
  • wai-ops: clippy::derived_hash_with_manual_eq (deny-by-default) fails clippy on both toolchains. No CI job runs clippy on this crate.
  • eoc-cascade hit_calibration_process_energy: it 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 its tree (741 passed).
  • rustfmt: no root is rustfmt-clean on main, and none is gated. The pin's rustfmt output equals 1.98.0's in all 46, so this PR adds no formatting drift; its own new lines are as rustfmt formats them.
  • Environment: 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 and wasmtime (wasm32 builds were checked).
  • The fuzz job (it uses its own nightly).

This PR's own CI run on the forge runners is the check for those.

Open PRs that carry the 1.98.0 pin

#426 (wai/pack-efficiency) and #438 (wai/cross-fabric, stacked on #426) still pin 1.98.0 in both rust-toolchain.toml files. They will need a rebase after this merges. #426 also edits .github/workflows/wai-pack.yml, whose install lines this PR changes, so expect a small conflict there. Neither PR was touched.

Not merged: this is for the owner's review.

🤖 Generated with Claude Code

Closed: superseded by #594, which carries the same pin rebuilt on current main

## What this changes This moves the toolchain pin from **Rust 1.98.0 to 1.99.1** (the current stable). It is a change-controlled pin; the owner approved it on 2026-10-22. There are two commits: 1. **clippy 1.99: fix what Rust 1.99.1's clippy newly reports.** These are the only diagnostics 1.99.1 reports that 1.98.0 did not, across every cargo root in the tree. 1.98.0's clippy also builds the fixed code and reports nothing new. - `clippy::assert_is_empty` (new in 1.99): 36 test-only sites in aac-core, access-core and eight openpay crates. `assert!(x.is_empty())` becomes `assert_eq!(x, [] as [T; 0])` (or `assert_ne!`, or `""` for strings), so a failure prints the value. aac-core and access-core `#![deny(clippy::all)]`, so their clippy run fails on 1.99.1 without this. **Judgment call:** clippy's own "MachineApplicable" suggestion does not compile at 18 of the 36 sites (it uses crate-relative paths that test modules cannot see, or a bare `[]` whose type cannot be inferred). Each site names its element type as its module sees it, and lines are wrapped as rustfmt wraps them. - `clippy::approx_constant` (deny-by-default) now knows `EULER_GAMMA` and `GOLDEN_RATIO` (stable since 1.94; the jouleclaw MSRV is 1.97). - jouleclaw-omni `mochi.rs`: `1.618_034` becomes `f32::consts::GOLDEN_RATIO`. They are the same f32 bits, so outputs do not change. This was failing standards-build's macOS gate `clippy -p jouleclaw-omni --features metal -- -D warnings`. - jouleclaw-outlier `c_factor`: `0.5772156649` becomes `f64::consts::EULER_GAMMA`. **Judgment call:** c(n) moves by 3.1e-12, because the literal was truncated and the isolation-forest paper's normalisation uses γ itself. Nothing else reads these scores. - smart-byte-rs `Cargo.lock`: async-trait 0.1.89 becomes 0.1.92 (with syn 3.0.9). 0.1.89 put `#[must_use]` on every method it generates, and clippy 1.99 now counts `Pin<Box<dyn Future>>` as must_use, so `double_must_use` fired at 9 trait methods. The attribute came from the macro, so the fix is the macro: 0.1.92, the version every other lockfile here already uses, no longer emits it. An incidental syn 2 to syn 1 move of data-encoding-macro-internal was put back, so the lock changes only what the bump needs. 2. **toolchain: Rust 1.98.0 to 1.99.1.** This covers both pins (`rust-toolchain.toml` and `eoc/eoc-rs/rust-toolchain.toml`) and every `1.98.0` the workflows install (34 files, 224 lines). Lines that record a measurement made on 1.98.0 are left alone: the standards-build "Verified … (rustc 1.98.0)" note, wai-conformance's LLD 22 note and its one-codegen-unit workaround, and the `rustc 1.98.0 (example)` strings in receipts and vectors. 1.99.1 ships LLD 23.1.1, so that workaround could be dropped after one x86_64 run at the CI path. ## Why - **rust-lang/rust#161441** (P-critical, I-miscompile, regression-from-stable-to-stable): rustc 1.98.0 can emit a vacant (null) method slot in a trait-object vtable, so a safe dynamic call jumps to address zero. That is undefined behaviour in safe code. RELEASES.md records the fix in 1.98.1. - **1.99.1** is the current stable (channel manifest dated 2026-10-15). It also fixes 1.99.0's own regressions: x86_64 FFI `bool` returns, `wcslen` on UEFI and embedded targets, and the rust-lld rpath on macOS. ## Evidence Everything ran on the build host (aarch64-apple-darwin) through `rb`. `rustup show` reports 1.99.1 as active, overridden by `rust-toolchain.toml` (`rustc 1.99.1 (58cf8f9c3 2026-10-13)`, LLVM 23.1.1). The baseline is `rustc 1.98.0 (88d9e12ae 2026-08-18)`. The scope is every cargo root the pin governs: 46 of the 49 tracked lockfiles. Two of the rest are vendored crates resolved inside their parents, and `wai/wai-rs/fuzz` uses its own pinned nightly. The final tree is main at `96117c570` plus these two commits. Main moved four times while this ran, so each root's row below names the newest tree it was run on. For each root in the older 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. The groups: 13 roots on the final tree, 12 on `1a465f23d`, 7 on `b16816671` (each with both commits), and 14 on `aa61ab3b9` with the pin change. Each root got: - **rustfmt:** `cargo fmt --all -- --check` on the pin and on 1.98.0 gives byte-identical output in all 46. CI gates no root on rustfmt, and none is rustfmt-clean on main. - **clippy:** `cargo clippy --locked --keep-going --workspace --all-targets` ran on both toolchains, with the diagnostics compared line by line. After commit 1, 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. - **tests:** `cargo test --workspace --locked`, plus each root's other CI steps that run on macOS arm64: feature-gated tests, conformance suites, release-profile tests, the aac page-set checks, and every `clippy -D warnings` gate (standards-build's macOS meter and omni lints, wai-pack, wai-quantum-cli default/no-default/metal, wai-quantum-service, wai-quantum-qpu, wai-quantum-desktop). - `scripts/check-lockfiles.sh` with cargo 1.99.1: all 47 lockfiles are current. `scripts/check-advisories.py` passes on the final tree. tokio is 1.54.1 in every lockfile cargo reads, which is patched for both RUSTSEC-2026-0386 and RUSTSEC-2026-0384. 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. **Totals:** `cargo test --workspace` ran in 43 roots (12,532 passed, 1 failed, 101 ignored). The 3 wasm32-only roots built for `wasm32-unknown-unknown`. The other CI steps passed (62 of 62). <details><summary>Per root</summary> | root | tree | rustfmt: pin vs 1.98.0 | clippy diagnostics: pin / 1.98.0 / only on pin | `cargo test --workspace`: passed / failed / ignored | other CI steps passing | |---|---|---|---|---|---| | `arl/arl-rs` | aa61ab3b9 | 51 hunks, identical | 13 / 13 / 0 | 58 / 0 / 0 | – | | `sense/sense-rs` | aa61ab3b9 | 112 hunks, identical | 0 / 0 / 0 | 45 / 0 / 0 | – | | `joulehook/joulehook-rs` | b16816671 | 12925 hunks, identical | 0 / 0 / 0 | 34 / 0 / 0 | – | | `joule-ui/joule-ui-rs` | aa61ab3b9 | 2777 hunks, identical | 2 / 2 / 0 | 72 / 0 / 0 | – | | `pool/pool-rs` | aa61ab3b9 | 78 hunks, identical | 0 / 0 / 0 | 74 / 0 / 0 | – | | `smart-byte/smart-byte-rs` | 1a465f23d | 642 hunks, identical | 57 / 57 / 0 | 708 / 0 / 0 | – | | `openpay` | 1a465f23d | 452 hunks, identical | 308 / 308 / 1 ² | 1951 / 0 / 6 | – | | `map/map-rs` | b16816671 | 248 hunks, identical | 1 / 1 / 0 | 228 / 0 / 0 | 1/1 | | `aac/aac-rs` | b16816671 | 3279 hunks, identical | 2 / 2 / 0 | 711 / 0 / 5 | 3/3 | | `aac/aac-rs/tools/symbols/bbox` | aa61ab3b9 | 3 hunks, identical | 0 / 0 / 0 | 0 / 0 / 0 | – | | `joulecontract/joulecontract-rs` | aa61ab3b9 | 3144 hunks, identical | 2 / 2 / 0 | 84 / 0 / 0 | – | | `proof/proof-rs` | aa61ab3b9 | 3097 hunks, identical | 0 / 0 / 0 | 173 / 0 / 0 | 2/2 | | `eoc/eoc-rs` | 1a465f23d | 802 hunks, identical | 33 / 33 / 0 | 741 / 0 / 3 | 2/2 | | `eoc/eoc-bench` | b16816671 | 802 hunks, identical | 0 / 0 / 0 | 15 / 0 / 0 | – | | `jcp/jcp-rs` | b16816671 | 2650 hunks, identical | 3 / 3 / 0 | 582 / 0 / 0 | 3/3 | | `sandbox/sandbox-rs` | b16816671 | 2650 hunks, identical | 0 / 0 / 0 | 440 / 0 / 0 | 3/3 | | `mesh/mesh-rs` | 1a465f23d | 12890 hunks, identical | 43 / 43 / 0 | 106 / 0 / 0 | 1/1 | | `jouledesk/jouledesk-rs` | 1a465f23d | 12711 hunks, identical | 0 / 0 / 0 | 44 / 0 / 1 | – | | `joule-code/joule-code-rs` | 96117c570 | 7356 hunks, identical | 19 / 19 / 0 | 571 / 0 / 1 | 7/7 | | `joule-code/joule-code-rs/crates/joule-moq-room` | 96117c570 | 26052 hunks, identical | 2 / 2 / 0 | 17 / 0 / 0 | – | | `joule-code/examples/l3-jouleclaw` | 1a465f23d | 17320 hunks, identical | 45 / 45 / 0 | 15 / 0 / 5 | – | | `joule-code/examples/transport-moqt` | 1a465f23d | 7322 hunks, identical | 0 / 0 / 0 | 2 / 0 / 0 | – | | `jouleclaw/jouleclaw-rs` | 1a465f23d | 12581 hunks, identical | 417 / 417 / 0 | 5017 / 0 / 74 | 10/10 | | `wai/byte-exact-conformance` | aa61ab3b9 | 1327 hunks, identical | 37 / 37 / 0 | 101 / 0 / 0 | 1/1 | | `wai/tools/ops-gpu-bench` | 1a465f23d | 30896 hunks, identical | 1 / 1 / 0 | 0 / 0 / 0 | 1/1 | | `wai/tools/quantum-meter` | 96117c570 | 16808 hunks, identical | 0 / 0 / 0 | 10 / 0 / 0 | 1/1 | | `wai/tools/quantum-wgsl-check` | 96117c570 | 4218 hunks, identical | 0 / 0 / 0 | 0 / 0 / 0 | – | | `wai/wai-live-web` | 1a465f23d | 18374 hunks, identical | 1 / 1 / 0 | 7 / 0 / 0 | 1/1 | | `wai/wai-ops` | aa61ab3b9 | 698 hunks, identical | 41 / 41 / 0 ¹ | 53 / 0 / 3 | 1/1 | | `wai/wai-ops/node` | aa61ab3b9 | 699 hunks, identical | 0 / 0 / 0 | wasm32 build ok | – | | `wai/wai-ops-gpu` | b16816671 | 829 hunks, identical | 0 / 0 / 0 | 4 / 1 / 0 ³ | 1/1 | | `wai/wai-ops-gpu/browser` | aa61ab3b9 | 837 hunks, identical | 0 / 0 / 0 | wasm32 build ok | – | | `wai/wai-pack` | 96117c570 | 18888 hunks, identical | 1 / 1 / 0 | 70 / 0 / 0 | 3/3 | | `wai/wai-quantum` | 96117c570 | 4172 hunks, identical | 6 / 6 / 0 | 82 / 0 / 2 | 1/1 | | `wai/wai-quantum-cli` | 96117c570 | 4366 hunks, identical | 0 / 0 / 0 | 8 / 0 / 0 | 5/5 | | `wai/wai-quantum-desktop` | 96117c570 | 4386 hunks, identical | 0 / 0 / 0 | 4 / 0 / 0 | 2/2 | | `wai/wai-quantum-qpu` | 96117c570 | 4311 hunks, identical | 0 / 0 / 0 | 21 / 0 / 0 | 1/1 | | `wai/wai-quantum-serve` | 96117c570 | 18344 hunks, identical | 2 / 2 / 0 | 10 / 0 / 0 | – | | `wai/wai-quantum-service` | 96117c570 | 4287 hunks, identical | 0 / 0 / 0 | 23 / 0 / 0 | 2/2 | | `wai/wai-relay` | 1a465f23d | 18287 hunks, identical | 1 / 1 / 0 | 0 / 0 / 0 | – | | `wai/wai-spz-gen` | 1a465f23d | 18294 hunks, identical | 1 / 1 / 0 | 0 / 0 / 0 | – | | `wai/wai-vector` | aa61ab3b9 | 594 hunks, identical | 1 / 1 / 0 | 81 / 0 / 0 | 3/3 | | `wai/wai-vector/wasm` | aa61ab3b9 | 603 hunks, identical | 1 / 1 / 0 ¹ | wasm32 build ok | – | | `wai/wai-verify` | aa61ab3b9 | 1399 hunks, identical | 5 / 5 / 0 | 36 / 0 / 0 | 1/1 | | `wai/wai-web` | 96117c570 | 18677 hunks, identical | 8 / 8 / 0 | 35 / 0 / 0 | 1/1 | | `wai/wai-rs` | 96117c570 | 18315 hunks, identical | 50 / 50 / 0 | 299 / 0 / 1 | 5/5 | ¹ clippy cannot finish on either toolchain: wai-ops has a deny-by-default `derived_hash_with_manual_eq`, and wai-vector/wasm's lib-test target clashes with its own `panic_impl`. For wai-vector/wasm, `clippy --lib --target wasm32-unknown-unknown` reports 0 diagnostics on both. ² This is the same lint at the same site (`op-dispute-evidence` evidence.rs:92), with its message reworded in 1.99. ³ This is a debug-profile `debug_assert` (exec.rs:187) on both toolchains. CI runs this crate in release only, and that passes (6/6). </details> ### Not green, and not from the toolchain (each reproduced on 1.98.0 or on main) - **wai-ops-gpu:** under the debug profile, `corpus` trips `debug_assert!(i32::try_from(v).is_ok())` on both toolchains. CI's release-only run passes. - **wai-ops:** `clippy::derived_hash_with_manual_eq` (deny-by-default) fails clippy on both toolchains. No CI job runs clippy on this crate. - **eoc-cascade `hit_calibration_process_energy`:** it 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 its tree (741 passed). - **rustfmt:** no root is rustfmt-clean on main, and none is gated. The pin's rustfmt output equals 1.98.0's in all 46, so this PR adds no formatting drift; its own new lines are as rustfmt formats them. - **Environment:** `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 and wasmtime (wasm32 builds were checked). - The fuzz job (it uses its own nightly). This PR's own CI run on the forge runners is the check for those. ## Open PRs that carry the 1.98.0 pin **#426** (`wai/pack-efficiency`) and **#438** (`wai/cross-fabric`, stacked on #426) still pin 1.98.0 in both `rust-toolchain.toml` files. They will need a rebase after this merges. #426 also edits `.github/workflows/wai-pack.yml`, whose install lines this PR changes, so expect a small conflict there. Neither PR was touched. Not merged: this is for the owner's review. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- **Closed:** superseded by #594, which carries the same pin rebuilt on current main 
These are the only lints clippy 1.99.1 reports that clippy 1.98.0 does not.
Every cargo root in the tree was compared on both toolchains (the evidence is
in the next commit). 1.98.0's clippy also builds every target of the fixed
code, and reports nothing it did not report before, so this commit stands
under either pin.

What changed, and why

- clippy::assert_is_empty is new in 1.99. 36 sites, all in test code
  (#[cfg(test)] modules; no lib or bin build reports any):
  aac-core and access-core, 23 sites; openpay's op-crypto-extra, op-emv,
  op-iso20022, op-reconciliation, op-routing, op-screening, op-settlement
  and op-tax, 13 sites. `assert!(x.is_empty())` becomes
  `assert_eq!(x, [] as [T; 0])`, `assert_ne!` for the negation, or `""` for
  strings, so a failure prints the value instead of only "false". aac-core and
  access-core are `#![deny(warnings)]` and `#![deny(clippy::all)]`, so without
  this their clippy run fails on 1.99.1.
  Judgment call: at 18 of the 36 sites, clippy's own "MachineApplicable"
  suggestion does not compile. It names local types by crate-relative path
  (`finder::Found`, which is not in scope in a test module), or offers a bare
  `[]` whose element type cannot be inferred. So each site names its element
  type as its own module sees it (`[] as [Found; 0]`, `[] as [f64; 0]`). The
  four lines rustfmt would wrap are wrapped the way rustfmt wraps them.

- clippy::approx_constant (deny-by-default) now knows EULER_GAMMA and
  GOLDEN_RATIO. Both are in std::f{32,64}::consts and stable since 1.94; the
  jouleclaw workspace MSRV is 1.97.
  - jouleclaw-omni, inference/architecture/mochi.rs: `1.618_034` becomes
    `std::f32::consts::GOLDEN_RATIO`. They are the same f32
    (1.61803400516510009765625), so the latents do not change. This file is
    in standards-build.yml's macOS gate (`cargo clippy -p jouleclaw-omni
    --features metal -- -D warnings`), which fails on 1.99.1 without the fix.
  - jouleclaw-outlier, c_factor: `0.5772156649` becomes
    `std::f64::consts::EULER_GAMMA`. Judgment call: the literal was
    truncated, so c(n) moves by 3.1e-12. The normalisation in the
    isolation-forest paper uses the Euler-Mascheroni constant itself, so this
    is the intended value. No other crate and no committed vector reads these
    scores, and the crate's tests pass unchanged.

- smart-byte-rs/Cargo.lock: async-trait 0.1.89 becomes 0.1.92, which adds
  syn 3.0.9 as its dependency. 0.1.89 put `#[must_use]` on every trait method
  it generates. clippy 1.99 now counts the returned `Pin<Box<dyn Future>>` as
  must_use already, so clippy::double_must_use fired at 9 #[async_trait] trait
  methods. The attribute there is the macro's, not ours, so the right fix is
  the macro: 0.1.92 no longer emits it, and every other lockfile in this tree
  already uses 0.1.92. A narrow `cargo update -p async-trait --precise 0.1.92`
  also moved data-encoding-macro-internal (which accepts syn >=1, <3) from syn
  2 to syn 1. That was put back to syn 2.0.117, as on main, so the lock
  changes only what the bump needs. `cargo update --workspace --locked` and
  scripts/check-lockfiles.sh accept it.

Left as they are

- openpay op-dispute-evidence evidence.rs:92 (clippy::double_must_use) is
  reported on 1.98.0 too. Only the message's wording changed in 1.99.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
toolchain: Rust 1.98.0 -> 1.99.1 (change-controlled pin)
All checks were successful
wai-quantum command line / command line · linux (pull_request) Successful in 1m10s
Details
wai-quantum dataflow member / member · dataflow device, simulated (pci 1e52:b140) (pull_request) Successful in 3m51s
Details
wai-quantum FPGA member / member · FPGA simulation absent (linux) (pull_request) Successful in 19s
Details
wai-quantum dataflow member / member · dataflow device, simulated (pci 1e52:401e) (pull_request) Successful in 4m47s
Details
wai-quantum Metal member / member · Metal absent (linux) (pull_request) Successful in 28s
Details
wai-quantum neural-processor member / member · neural processor absent (linux) (pull_request) Successful in 19s
Details
wai-quantum OpenCL member / member · OpenCL absent (linux) (pull_request) Successful in 19s
Details
wai-quantum-qpu / clients against their contracts (linux) (pull_request) Successful in 20s
Details
wai-quantum service / service · linux (pull_request) Successful in 39s
Details
wai-quantum tensor-engine member / member · tensor engine, the kernel toolchain's simulator (linux) (pull_request) Successful in 8m4s
Details
wai-quantum matrix-extension member / member · matrix extension, emulated (aarch64 Linux) (pull_request) Successful in 34s
Details
wai-quantum studio and desktop / studio · browser (pull_request) Successful in 2m20s
Details
wai-quantum portable tensor program / tensor program · CPU, mutants, GPU builds (pull_request) Successful in 40s
Details
wai-quantum signal processor / processor and member · signal processor, emulated (pull_request) Successful in 14m50s
Details
wai-quantum CPU vector units / member · vector unit, rvv 1024-bit (riscv64, emulated) (pull_request) Successful in 28s
Details
wai-quantum CPU vector units / member · vector unit, sve 128-bit (aarch64, emulated) (pull_request) Successful in 45s
Details
wai-quantum CPU vector units / member · vector unit, rvv 128-bit (riscv64, emulated) (pull_request) Successful in 34s
Details
wai-quantum CPU vector units / member · vector unit, sve 2048-bit (aarch64, emulated) (pull_request) Successful in 16s
Details
wai-quantum CPU vector units / member · vector unit, avx2 (x86_64 silicon) (pull_request) Successful in 18s
Details
wai-quantum CPU vector units / member · vector unit, sve 512-bit (aarch64, emulated) (pull_request) Successful in 21s
Details
wai-quantum WebGPU member / member · software Vulkan (linux) (pull_request) Successful in 2m16s
Details
wai-quantum WebGPU member / shader checks · browser build · wasip2 inertness · MSRV (pull_request) Successful in 3m13s
Details
wai-vector vector graphics / linux-x86_64 (pull_request) Successful in 2m21s
Details
wai-vector vector graphics / wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m8s
Details
wai-vector vector graphics / wasm32 under Node (pull_request) Successful in 26s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Successful in 5m20s
Details
wai-vector vector graphics / fuzz, peak allocation, comparison count (pull_request) Successful in 20s
Details
wai-vector vector graphics / wasm32 in three browser engines (pull_request) Successful in 3m1s
Details
wai-vector vector graphics / independent checker (Python) (pull_request) Successful in 3m45s
Details
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Successful in 3m59s
Details
cf0665493e 
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.
- 34 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
  (224 lines).
- 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 at 96117c570 plus 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 after 1a465f23d,
    and every root that consumes such a crate by path.
  - 12 roots on 1a465f23d plus these two commits.
  - 7 roots on b16816671 plus these two commits.
  - 14 roots on aa61ab3b9 plus 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]>
dcharlot closed this pull request 2026-11-03 01:17:41 -05:00
All checks were successful
wai-quantum WebGPU member / member · DX12 and Vulkan (cbio-windows) (pull_request) Successful in 12m54s
Details
jouleclaw fabrics / cuda (linux, RTX 4050 + Vulkan loader) (pull_request) Successful in 27s
Details
jouleclaw fabrics / vulkan (linux, RTX 4050 + Vulkan loader) (pull_request) Successful in 17s
Details
jouleclaw fabrics / metal (macOS, Apple GPU) (pull_request) Successful in 1m1s
Details
joule-code conformance gate / Build + round-trip C1-C4 vectors (pull_request) Successful in 3m5s
Details
joule-moq-room room service / joule-moq-room · does this change touch it (pull_request) Successful in 7s
Details
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 1m1s
Details
wai-ops differential (nightly) / differential · debug (pull_request) Successful in 2m49s
Details
wai-ops differential (nightly) / differential · release (pull_request) Successful in 4m6s
Details
wai-quantum on every processor / emulated · aarch64-unknown-linux-gnu (pull_request) Successful in 2m49s
Details
wai-quantum on every processor / emulated · armv7-unknown-linux-gnueabihf (pull_request) Successful in 2m12s
Details
joule-code conformance gate / joule-moq-relay, every target (pull_request) Successful in 1m51s
Details
wai-quantum on every processor / emulated · loongarch64-unknown-linux-gnu (pull_request) Successful in 3m42s
Details
wai-quantum on every processor / emulated · powerpc64-unknown-linux-gnu (pull_request) Successful in 5m10s
Details
wai-quantum on every processor / emulated · powerpc64le-unknown-linux-gnu (pull_request) Successful in 5m43s
Details
wai-quantum on every processor / emulated · riscv64gc-unknown-linux-gnu (pull_request) Successful in 3m56s
Details
wai-quantum on every processor / emulated · s390x-unknown-linux-gnu (pull_request) Successful in 3m56s
Details
wai-quantum on every processor / emulated · sparc64-unknown-linux-gnu (pull_request) Successful in 5m57s
Details
wai-web reach builds / wai-web reach · does this change touch it (pull_request) Successful in 7s
Details
wai-quantum on every processor / emulated · i686-unknown-linux-gnu (pull_request) Successful in 4m6s
Details
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 6s
Details
wai cross-architecture byte-equality / does this change touch it (pull_request) Successful in 7s
Details
WAI conformance / does this change touch it (pull_request) Successful in 8s
Details
wai formal verification (integer core) / does this change touch it (pull_request) Successful in 7s
Details
WAI energy receipts / does this change touch it (pull_request) Successful in 8s
Details
WAI HTTP delivery / WAI HTTP · does this change touch it (pull_request) Successful in 6s
Details
WAI neural decoders end-to-end / does this change touch it (pull_request) Successful in 11s
Details
WAI JPEG-AI whole decode (pinned inputs, required) / does this change touch it (pull_request) Successful in 12s
Details
WAI neural sink gates / does this change touch it (pull_request) Successful in 11s
Details
wai-ops integer operators / does this change touch it (pull_request) Successful in 18s
Details
wai-ops-gpu integer operators on GPUs / does this change touch it (pull_request) Successful in 19s
Details
wai-pack / wai-pack · does this change touch it (pull_request) Successful in 20s
Details
wai-quantum command line / does this change touch it (pull_request) Successful in 12s
Details
wai-quantum CUDA member / does this change touch it (pull_request) Successful in 13s
Details
wai-quantum dataflow member / does this change touch it (pull_request) Successful in 12s
Details
wai-quantum FPGA member / does this change touch it (pull_request) Successful in 15s
Details
wai-quantum HIP member / does this change touch it (pull_request) Successful in 16s
Details
wai-quantum signal processor / does this change touch it (pull_request) Successful in 20s
Details
wai-quantum npu-cores member / does this change touch it (pull_request) Successful in 13s
Details
wai-quantum Metal member / does this change touch it (pull_request) Successful in 16s
Details
wai-quantum neural-processor member / does this change touch it (pull_request) Successful in 13s
Details
wai-quantum OpenCL member / does this change touch it (pull_request) Successful in 8s
Details
wai-quantum-qpu / does this change touch it (pull_request) Successful in 9s
Details
wai-quantum service / does this change touch it (pull_request) Successful in 8s
Details
wai-quantum HIP member / member · HIP (framework-128gb) (pull_request) Successful in 29s
Details
wai-quantum tensor-engine member / does this change touch it (pull_request) Successful in 6s
Details
wai-quantum matrix-extension member / does this change touch it (pull_request) Successful in 8s
Details
wai-quantum studio and desktop / does this change touch it (pull_request) Successful in 9s
Details
wai-quantum CUDA member / member · CUDA (jetson-hub) (pull_request) Successful in 55s
Details
wai-quantum portable tensor program / does this change touch it (pull_request) Successful in 6s
Details
wai-quantum WebGPU member / does this change touch it (pull_request) Successful in 7s
Details
wai-quantum CPU vector units / does this change touch it (pull_request) Successful in 8s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / does this change touch it (pull_request) Successful in 7s
Details
wai-vector vector graphics / does this change touch it (pull_request) Successful in 6s
Details
wai-web wasm32 / does this change touch it (pull_request) Successful in 6s
Details
joule-code conformance gate / joule-moq-ingest, every target (pull_request) Successful in 2m14s
Details
wai-quantum OpenCL member / member · OpenCL GPU and CPU (jetson-hub) (pull_request) Successful in 1m0s
Details
wai-quantum npu-cores member / member · npu-cores, neural processor (framework-128gb silicon) (pull_request) Successful in 1m17s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 3m14s
Details
wai-quantum OpenCL member / member · OpenCL GPU (framework-128gb) (pull_request) Successful in 17s
Details
wai-quantum portable tensor program / tensor program · integrated GPU (framework-128gb) (pull_request) Successful in 9s
Details
wai-quantum CPU vector units / member · vector units, avx2 and avx512 (framework-128gb silicon) (pull_request) Successful in 12s
Details
wai-quantum portable tensor program / tensor program · GPUs (jetson-hub) (pull_request) Successful in 53s
Details
wai-quantum WebGPU member / member · integrated GPU, Vulkan (framework-128gb) (pull_request) Successful in 8m7s
Details
wai cross-architecture byte-equality / macos-arm64 (reference) (pull_request) Successful in 23s
Details
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 3m49s
Details
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 21s
Details
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 43s
Details
standards workspaces build + test / macOS energy backends (pull_request) Successful in 9m51s
Details
WAI energy receipts / energy receipts · macos (pull_request) Successful in 5m42s
Details
wai-ops integer operators / macos-arm64 (pull_request) Successful in 59s
Details
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 15m36s
Details
wai-pack / wai-pack · macos (pull_request) Successful in 1m19s
Details
wai-ops-gpu integer operators on GPUs / Metal GPU and browser WebGPU (macos) (pull_request) Successful in 4m35s
Details
wai-quantum dataflow member / member · dataflow device absent (macos) (pull_request) Successful in 13s
Details
wai-quantum command line / command line · macos (pull_request) Successful in 32s
Details
wai-quantum Metal member / member · Metal (macos) (pull_request) Successful in 28s
Details
wai-quantum FPGA member / member · FPGA datapath, simulated (macos) (pull_request) Successful in 1m11s
Details
wai-quantum OpenCL member / member · OpenCL GPU (macos) (pull_request) Successful in 21s
Details
wai-quantum service / service · macos (pull_request) Successful in 46s
Details
wai-quantum matrix-extension member / member · matrix extension absent (macos) (pull_request) Successful in 10s
Details
wai-quantum studio and desktop / desktop app · macos (pull_request) Successful in 2m11s
Details
wai-quantum portable tensor program / tensor program · Metal and the arm64 CPU (macos) (pull_request) Successful in 16s
Details
wai-quantum CPU vector units / member · vector unit absent (macos) (pull_request) Successful in 13s
Details
wai formal verification (integer core) / kani (rans64-t2) (pull_request) Successful in 19m0s
Details
wai-quantum WebGPU member / member · browser WebGPU (macos) (pull_request) Successful in 1m43s
Details
wai-quantum WebGPU member / member · Metal (macos) (pull_request) Successful in 2m37s
Details
wai-quantum neural-processor member / member · neural processor (macos) (pull_request) Successful in 9m27s
Details
wai-vector vector graphics / macos-arm64 (pull_request) Successful in 2m21s
Details
wai-quantum WebGPU member / member · discrete GPU, Vulkan (jetson-hub) (pull_request) Successful in 57m16s
Details
joule-moq-room room service / joule-moq-room, every target (pull_request) Successful in 1m43s
Details
wai cross-architecture byte-equality / linux-aarch64 (pull_request) Successful in 31s
Details
standards workspaces build + test / joulecontract-rs (joulecontract/joulecontract-rs, joulecontract-rs, linux-arm64, true) (pull_request) Successful in 1m5s
Details
standards workspaces build + test / jouleclaw-rs (-nodebug, jouleclaw/jouleclaw-rs, -p jouleclaw-energy --features rapl,nvml, jouleclaw-rs, linux-arm64, -C target-feature=+fp16) (pull_request) Successful in 3m32s
Details
standards workspaces build + test / aac-rs (aac-conformance, aac/aac-rs, aac-rs, linux-arm64) (pull_request) Successful in 3m22s
Details
standards workspaces build + test / map-rs (map-conformance, map/map-rs, map-rs, linux-arm64) (pull_request) Successful in 1m6s
Details
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 19s
Details
standards workspaces build + test / mesh-rs (mesh/mesh-rs, -p mesh-engine-gguf -p mesh-openai --features mesh-engine-gguf/gguf,mesh-openai/server, mesh-rs, linux-arm64) (pull_request) Successful in 1m4s
Details
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 11s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 26s
Details
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 4m29s
Details
standards workspaces build + test / openpay (openpay, openpay, linux-arm64) (pull_request) Successful in 3m15s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 1m37s
Details
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 14m57s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Successful in 13m55s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 40m27s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Successful in 13m37s
Details
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 5s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m38s
Details
wai-web reach builds / wai-web reach builds · the package of record, every output as recorded (pull_request) Successful in 2m52s
Details
wai cross-architecture byte-equality / linux-x86_64 (pull_request) Successful in 27s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 1m4s
Details
standards workspaces build + test / arl-rs (arl/arl-rs, arl-rs, linux) (pull_request) Successful in 1m20s
Details
wai-web reach builds / wai-web reach builds · this tree's wai-web, every rung on its engine line (pull_request) Successful in 4m27s
Details
standards workspaces build + test / eoc-rs (eoc/eoc-rs, -p eoc-meter --features cuda, eoc-rs, linux) (pull_request) Successful in 1m57s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Successful in 46m39s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Successful in 47m43s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Successful in 46m58s
Details
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 1m38s
Details
wai-ops integer operators / linux-aarch64 (pull_request) Successful in 1m9s
Details
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 1m15s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 23s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m29s
Details
wai-quantum HIP member / member · HIP absent (linux-arm64) (pull_request) Successful in 23s
Details
standards workspaces build + test / joulehook-rs (joulehook/joulehook-rs, joulehook-rs, linux) (pull_request) Successful in 1m16s
Details
standards workspaces build + test / pool-rs (pool/pool-rs, pool-rs, linux) (pull_request) Successful in 1m11s
Details
wai-quantum npu-cores member / member · npu-cores absent (linux-arm64) (pull_request) Successful in 21s
Details
wai-quantum tensor-engine member / member · tensor engine absent (linux-arm64) (pull_request) Successful in 19s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m19s
Details
standards workspaces build + test / proof-rs (proof-conformance, proof/proof-rs, proof-rs, linux, true) (pull_request) Successful in 1m39s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 4m9s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 8m14s
Details
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, -p sandbox-tee --features amd-kds,intel-pcs, sandbox-rs, linux) (pull_request) Successful in 2m42s
Details
standards workspaces build + test / sense-rs (sense/sense-rs, sense-rs, linux) (pull_request) Successful in 1m12s
Details
wai-vector vector graphics / linux-aarch64 (pull_request) Successful in 2m29s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Successful in 14m56s
Details
standards workspaces build + test / smart-byte-rs (smart-byte/smart-byte-rs, smart-byte-rs, linux) (pull_request) Successful in 4m7s
Details
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 2m6s
Details
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 27s
Details
wai formal verification (integer core) / every harness in one shard (pull_request) Successful in 14s
Details
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 14m51s
Details
wai formal verification (integer core) / kani (arith) (pull_request) Successful in 12m58s
Details
wai formal verification (integer core) / kani (plan) (pull_request) Successful in 6m29s
Details
wai formal verification (integer core) / kani (sound) (pull_request) Successful in 10m43s
Details
wai formal verification (integer core) / kani (stage) (pull_request) Successful in 3m32s
Details
wai formal verification (integer core) / kani (stage-long) (pull_request) Successful in 23m32s
Details
wai formal verification (integer core) / kani (isqrt512) (pull_request) Successful in 51m59s
Details
wai formal verification (integer core) / kani (integer-core) (pull_request) Successful in 6m20s
Details
WAI energy receipts / energy receipts · linux (pull_request) Successful in 9m13s
Details
WAI neural decoders end-to-end / synthetic fixtures → Rust decode → reference (±4) (pull_request) Successful in 1m19s
Details
WAI neural sink gates / model-free refusals of the neural sink (pull_request) Successful in 1m13s
Details
WAI JPEG-AI whole decode (pinned inputs, required) / fetch pinned JPEG-AI inputs → whole decode + pixel hash, required (pull_request) Successful in 8m47s
Details
wai-ops integer operators / linux-x86_64 (pull_request) Successful in 54s
Details
wai-ops integer operators / wasm32-wasip2 (wasmtime) (pull_request) Successful in 31s
Details
wai-ops integer operators / wasm32 under Node (pull_request) Successful in 22s
Details
wai-ops integer operators / independent checker (Python) (pull_request) Successful in 13s
Details
wai-pack / wai-pack · linux (pull_request) Successful in 1m27s
Details
wai-ops-gpu integer operators on GPUs / builds · no adapter is not a pass (linux) (pull_request) Successful in 2m11s
Details
wai-quantum CUDA member / member · CUDA absent (linux) (pull_request) Successful in 23s
Details
wai-quantum command line / command line · linux (pull_request) Successful in 1m10s
Details
wai-quantum dataflow member / member · dataflow device, simulated (pci 1e52:b140) (pull_request) Successful in 3m51s
Details
wai-quantum FPGA member / member · FPGA simulation absent (linux) (pull_request) Successful in 19s
Details
wai-quantum dataflow member / member · dataflow device, simulated (pci 1e52:401e) (pull_request) Successful in 4m47s
Details
wai-quantum Metal member / member · Metal absent (linux) (pull_request) Successful in 28s
Details
wai-quantum neural-processor member / member · neural processor absent (linux) (pull_request) Successful in 19s
Details
wai-quantum OpenCL member / member · OpenCL absent (linux) (pull_request) Successful in 19s
Details
wai-quantum-qpu / clients against their contracts (linux) (pull_request) Successful in 20s
Details
wai-quantum service / service · linux (pull_request) Successful in 39s
Details
wai-quantum tensor-engine member / member · tensor engine, the kernel toolchain's simulator (linux) (pull_request) Successful in 8m4s
Details
wai-quantum matrix-extension member / member · matrix extension, emulated (aarch64 Linux) (pull_request) Successful in 34s
Details
wai-quantum studio and desktop / studio · browser (pull_request) Successful in 2m20s
Details
wai-quantum portable tensor program / tensor program · CPU, mutants, GPU builds (pull_request) Successful in 40s
Details
wai-quantum signal processor / processor and member · signal processor, emulated (pull_request) Successful in 14m50s
Details
wai-quantum CPU vector units / member · vector unit, rvv 1024-bit (riscv64, emulated) (pull_request) Successful in 28s
Details
wai-quantum CPU vector units / member · vector unit, sve 128-bit (aarch64, emulated) (pull_request) Successful in 45s
Details
wai-quantum CPU vector units / member · vector unit, rvv 128-bit (riscv64, emulated) (pull_request) Successful in 34s
Details
wai-quantum CPU vector units / member · vector unit, sve 2048-bit (aarch64, emulated) (pull_request) Successful in 16s
Details
wai-quantum CPU vector units / member · vector unit, avx2 (x86_64 silicon) (pull_request) Successful in 18s
Details
wai-quantum CPU vector units / member · vector unit, sve 512-bit (aarch64, emulated) (pull_request) Successful in 21s
Details
wai-quantum WebGPU member / member · software Vulkan (linux) (pull_request) Successful in 2m16s
Details
wai-quantum WebGPU member / shader checks · browser build · wasip2 inertness · MSRV (pull_request) Successful in 3m13s
Details
wai-vector vector graphics / linux-x86_64 (pull_request) Successful in 2m21s
Details
wai-vector vector graphics / wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m8s
Details
wai-vector vector graphics / wasm32 under Node (pull_request) Successful in 26s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Successful in 5m20s
Details
wai-vector vector graphics / fuzz, peak allocation, comparison count (pull_request) Successful in 20s
Details
wai-vector vector graphics / wasm32 in three browser engines (pull_request) Successful in 3m1s
Details
wai-vector vector graphics / independent checker (Python) (pull_request) Successful in 3m45s
Details
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Successful in 3m59s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!472
No description provided.