Compression mishandles errors from underlying reader

[dropbox]

Compression mishandles errors from underlying reader

[danielrh]

Thanks for the bug report!
I've fixed it in version 3.1.8 with a test (just pushed)
Please let me know if the results are not what you'd expect.

Out of curiosity, which of your projects ran into this? Does the test you were doing pass now?

[tylerhawkes]

Sorry about the delay. It appears to work as expected now.
The project is on an embedded platform where we're trying to losslessly compress artifacts for uploading and analysis later as much as possible to save on bandwidth. I get between the readers and writers and determine if the compression ratio is after some percentage of the reads is too high or taking too long and raise my own error to not let it go forever.
Brotli levels 10 and 11 take an incredibly long time between calls to read or to write. It would be nice to set a maximum time limit to write calls even if you wrote out a buffer of zero length because then I can cancel the operation with better time granularity.