joule-moq-relay, wai-remote-host: build on Windows; the cascade test takes a metered hop #511
Loading…
Reference in a new issue
No description provided.
Delete branch "wai/dvr-windows-positional"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The release
wai-v0.3.0built every leg except Windows:joule-moq-relayfailed to compile there, because the DVR reads and writes its segments throughstd::os::unix::fs::FileExt(read_exact_at,write_all_at).seek_readandseek_write, each looping to the full length. They move the file's cursor, which the DVR never reads: every segment write is positional. Unix is unchanged.three_relays_in_a_chainasserted that every hop signs the unmetered marker. Where the relay reads its own counter (macOS, since the relay meters itself), each hop signs OnChipCounter instead, so the test failed on every run there. CI runs it only on linux-arm64, which has no counter. It now takes either form;relay_energy.rsstill tests the metered figure itself.Checked on the build host:
cargo check --target x86_64-pc-windows-gnupasses for the four released Windows binaries: the relay, the room, the remote host andwai-pack. Thewindows-gnutarget has the samestd::os::windowsAPI asmsvc.cargo test -p joule-moq-relaypasses every test, including the cascade test, which failed four runs out of four before the change.joule-moq-remotepasses its clippy (-D warnings) and its tests.🤖 Generated with Claude Code