Due to an issue in Flatbuffers (https://github.com/google/flatbuffers/issues/8245) when we call consumer.setPreferredLayers() with temporalLayer: 0 (or transport.consume() with temporalLayer: 0 in preferredLayers), we are NOT passing temporalLayer to the worker so it selects the highest available temporal layer instead.
This PR tests that use case in both Node and Rust, and tests should fail (only in Node) until the FlatBuffers issue is resolved.
FlatBuffers 24.3.6 (with the fix) has been released. The NPM version is already available. Ongoing work in Meson WrapDB to update FlatBuffers there: https://github.com/mesonbuild/wrapdb/pull/1441
consumer.setPreferredLayers()
withtemporalLayer: 0
(ortransport.consume()
withtemporalLayer: 0
inpreferredLayers
), we are NOT passingtemporalLayer
to the worker so it selects the highest available temporal layer instead.