ef82a05a3a
The sweep behind this branch found one check demanding an exact match where the contract permits a short answer, and four that were right to demand one. The question that separates them belongs where the next check gets written, not only in a run report: is the far side reporting what it did, or being held to a requirement? Worker.Acknowledge is the only reply of the first kind here, because ipc-v1 section 5 makes it idempotent. The commit and batch checks are the second kind and are named so nobody loosens them later in the name of tolerance; they are what make a partial commit and an incomplete batch fail. |
||
|---|---|---|
| .. | ||
| .cargo | ||
| crates | ||
| golden | ||
| tools | ||
| vendor/binjgb | ||
| Cargo.lock | ||
| Cargo.toml | ||
| flysim.toml.example | ||
| rust-toolchain.toml | ||