These errors always seem to happen before a given streaming file has finished cacheing as per ‘grep streaming-std RoonServer_log.txt’. The first log above did not have this error, but again, the streaming file had not finished reading/cacheing. So maybe it just timed out instead of creating what looks to be a data error. Along with other similar reports like Tidal playback randomly skips to next track part way through playback, and the nature of the stack traces, I think this has to do with the connection between my roon core and Qobuz.
I have restarted my router, disabled EEE (energy efficient ethernet). I have a pretty vanilla setup and speed tests from the roon core server show 2 ms latency, 800Mbps + down, and almost 1Gbps up. Weird …