| Filename | Latest commit message | Latest commit date |
|---|---|---|
7eee267a06
All checks were successful
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m56s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m19s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 3m37s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m12s
standards workspaces build + test / aac-rs (pull_request) Successful in 52s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m7s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 2m54s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m34s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 2m3s
standards workspaces build + test / map-rs (pull_request) Successful in 2m24s
standards workspaces build + test / mesh-rs (pull_request) Successful in 1m52s
standards workspaces build + test / arl-rs (pull_request) Successful in 18m13s
standards workspaces build + test / openpay (pull_request) Successful in 6m30s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 24m22s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 40m4s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 12m31s
standards workspaces build + test / sense-rs (pull_request) Successful in 18m28s
The replay test opened with the same `if !dir.exists() { return; }` the other
two vector-pack tests had — and that early return fires *before* the
`replayed >= 11` guard at the end of the function. So a missing or moved pack
reported green, which is precisely the case that guard was written to catch. I
had described the test as anti-vacuous; with that return in place it was not.
`main` has since replaced the same pattern in `vector_pack_tests` with an
assertion, on the grounds that this crate is not published and so only ever runs
in-repo where the pack is always present. That reasoning applies unchanged here,
so the replay now asserts too, and the three pack tests in this file agree.
Verified in both directions rather than one:
- pack present: 10 passed
- pack moved aside: the replay FAILS, naming the path it could not find
Before this change the second case passed. The pack was restored and confirmed
byte-identical with `git status`, not by assumption.
Co-Authored-By: Claude Opus 5 <[email protected]>
|
||
| .. | ||
| crates | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||