Klaus Post
Klaus Post
(fixed...)
@harshavardhana No worries. It is not going anywhere.
@harshavardhana @vadmeste Well... We don't have "shutdown" anymore. How does this work, then?
It is injecting the logger with the `testing.T` to capture log errors. This is testing only. You are welcome to see if you can come up with a cleaner solution.
Tracing only the call itself will not show what is going on, so filtering is not too feasible here. You can try `--response-duration=20ms` to filter out the fastest requests -...
I released the current changes. As for #40 it leads to infinite allocations as I pointed out and asking to revert these changes. But I can follow up.
@yoavj-arpeely This library shouldn't be used for small compression tasks, so largely this shouldn't affect anything. You are welcome to send a PR.
@cyphar Thank you for looking through my ancient code. I remember it being quite painful when I looked through it a year ago.
> This does have the downside that the read-ahead goroutine can now end up allocating more blocks than the user requested @cyphar It this without limit? There must be a...
@cyphar It would be great if you could look at that. Unbounded decompression is an issue. Thanks!