Skip to content

stream: ensure pipeline always destroys streams

There was an edge case where an incorrect assumption was made in regards to whether eos/finished means that the stream is actually destroyed or not.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports

Loading