| Filename | Latest commit message | Latest commit date |
|---|---|---|
19904251b7
All checks were successful
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 59s
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 5s
repository checks / lockfiles, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 37s
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 3m18s
standards workspaces build + test / joulecontract-rs (joulecontract/joulecontract-rs, joulecontract-rs, linux-arm64, true) (pull_request) Successful in 1m11s
standards workspaces build + test / arl-rs (arl/arl-rs, arl-rs, linux) (pull_request) Successful in 1m13s
standards workspaces build + test / aac-rs (aac-conformance, aac/aac-rs, aac-rs, linux-arm64) (pull_request) Successful in 4m18s
standards workspaces build + test / map-rs (map-conformance, map/map-rs, map-rs, linux-arm64) (pull_request) Successful in 1m19s
standards workspaces build + test / eoc-rs (eoc/eoc-rs, -p eoc-meter --features cuda, eoc-rs, linux) (pull_request) Successful in 2m10s
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 2m2s
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 1m27s
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 1m11s
standards workspaces build + test / joulehook-rs (joulehook/joulehook-rs, joulehook-rs, linux) (pull_request) Successful in 1m14s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 5m6s
standards workspaces build + test / pool-rs (pool/pool-rs, pool-rs, linux) (pull_request) Successful in 1m7s
standards workspaces build + test / proof-rs (proof-conformance, proof/proof-rs, proof-rs, linux, true) (pull_request) Successful in 1m50s
standards workspaces build + test / sense-rs (sense/sense-rs, sense-rs, linux) (pull_request) Successful in 1m11s
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, sandbox-rs, linux) (pull_request) Successful in 2m25s
standards workspaces build + test / openpay (openpay, openpay, linux-arm64) (pull_request) Successful in 8m30s
standards workspaces build + test / smart-byte-rs (smart-byte/smart-byte-rs, smart-byte-rs, linux) (pull_request) Successful in 4m27s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 8m25s
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 2m52s
10 -> 0, and the `-D warnings` step now lints loader-gguf under `rayon fabric-meter` as well as on default, plus backend-apple on its own. That closes the per-configuration lint hole #373 opened and #414 halved. The last ten, all in mps_matmul.rs: - `struct PipelineCell` with its `unsafe impl Send`/`Sync` was never constructed and mentioned nowhere else -- scaffolding for a OnceLock wrapper the pipelines ended up doing directly. Removed, and the space reused for a `KeepAlive` alias, which is what the two `type_complexity` warnings wanted: the inline form is three generic layers deep and appeared twice. - `DeviceKvCache` had a public `len` and no `is_empty`. - three `let qk_pipe = qk_pipe;` no-op rebindings from a refactor. - `too_many_arguments` and `needless_range_loop` allowed crate-wide, the same two decisions omni and loader-gguf already record and for the same reasons: a GPU dispatch signature is its kernel's parameter list, and these kernels walk several buffers at one index. The comment this replaces in standards-build.yml claimed the fabric-meter configuration could not be gated because backend-apple's warnings "are unused in THAT configuration and needed in others, so they want cfg work rather than deletion". Measuring the crate directly refuted both halves: it has no `[features]` at all, so there is one configuration, and the count was 84 rather than the 43 that leaked through loader-gguf's lint. Verified: all ten lint specs in the step pass, 37 backend-apple tests (32 pass, 5 ignored), 343 loader-gguf tests, 77 omni tests. Co-Authored-By: Claude Opus 5 <[email protected]> |
||
| .. | ||
| workflows | ||