enricobuehler 18fdc4cc6b fix(encode): the PyroWave worker proxy never wrote distrust_references, so its own guard test failed ...

Pre-existing on main, inherited by merging it. `distrust_references` arrived with the RFI
anchor work in `93c1ed07`; `RemotePyroWave` did not gain it, and the trait-coverage test
beside the impl caught exactly that.

The answer is a no-op, for the same reason `invalidate_ref_frames` returns false and
`request_keyframe` does nothing: PyroWave is intra-only, so every AU is already a
keyframe and there is no RFI anchor trust to withdraw. The in-process encoder reaches
the same answer by inheriting the trait default, and that is fine there.

It is not fine HERE, which is the point the guard test is making. This type is a proxy:
an inherited default means the worker never hears the call, so a method that does
something is silently dead on every worker-backed session while the in-process path
keeps working. The test therefore requires the method to be WRITTEN, so that "nothing to
do" is a visible decision rather than an omission. Written, with the reason.

Verified with CI's exact command — `cargo test -p pf-encode --features
nvenc,vulkan-encode,pyrowave` — 122 passed, and clippy clean under the same features.

2026-08-16 13:39:15 +02:00

..

src

fix(encode): the PyroWave worker proxy never wrote distrust_references, so its own guard test failed

2026-08-16 13:39:15 +02:00

Cargo.toml

chore(deps): libloading 0.8 -> 0.9 across the five crates that dlopen

2026-08-13 14:10:10 +02:00