enricobuehlerandClaude Fable 5
5807d3a8a6
ci / rust (push) Canceled after 0s
ci / web (push) Canceled after 0s
ci / docs-site (push) Canceled after 0s
docker / builders (--build-arg FEDORA_VERSION=44, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm, -f44) (push) Canceled after 0s
docker / builders (ci/android-ci.Dockerfile, punktfunk-android-ci) (push) Canceled after 0s
docker / builders (ci/arch-ci.Dockerfile, punktfunk-arch-ci) (push) Canceled after 0s
docker / builders (ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Canceled after 0s
docker / builders (ci/rust-ci-noble.Dockerfile, punktfunk-rust-ci-noble) (push) Canceled after 0s
docker / builders (ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Canceled after 0s
docker / builders-arm64cross (push) Canceled after 0s
docker / apps (., web/Dockerfile, punktfunk-web) (push) Canceled after 0s
docker / apps (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Canceled after 0s
docker / deploy-docs (push) Canceled after 0s
ci / rust-arm64 (push) Successful in 2m24s
49bc93cd grew seal_streamed_chunk a slice_end parameter and updated every
caller except this one — the Linux clippy leg has been red since (run
10615+). false = the legacy full-FEC-block granularity the harness always
exercised; its loopback client never advertises the P2 slice wire.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>loss-harness
A FEC loss-resilience sweep for punktfunk-core. It
drives access units through the in-process loopback at increasing packet-loss rates — for both FEC
schemes (GF(2⁸) and GF(2¹⁶)) — and reports how many frames survive.
It's a pure-software stand-in for tc netem: no network, no root, runs anywhere punktfunk-core
builds. Use it to sanity-check the FEC before reaching for the real punktfunk/1 harness (which adds
tc netem jitter/reorder on the UDP path).
cargo run -p loss-harness # from the repo root
Part of the measurement tooling (punktfunk-planning: implementation-plan.md §10), alongside
latency-probe.