[Probably a bug] Streaming about hyper-express HOT 6 CLOSED

I found out that offset in drain and lastOffset is the same value

from hyper-express.

Yeah, I used to actually have that sliced chunk being served for backpressuring but it's a very weird implementation and it turned out that chunk slicing was not needed because the write() method buffers the chunk under the hood anyways. So essentially, you should serve the next chunk after backpressure relieves rather than serve the same chunk but sliced. If you find this behavior to be incorrect, feel free to link the test code to recreate the bug in hyper-express and I'd be glad to push a fix.

from hyper-express.

The issue is stream hangs on slow internet connection when streaming a few megabytes in few files. I'm using this method stream to stream static files, the issue appears when I'm testing it on a production server over internet. So you may try to reproduce it by serving multiple large images over network (you may try to throttle the bandwidth in browser devtools). It may appear in future when you will be developing a middleware for static files serving

from hyper-express.

I see, I'll try to recreate this myself. If you end up writing a snippet to simulate this bug with high probability feel free to share.

from hyper-express.

I think i finally fixed this method issues for both: streams with size and without size

from hyper-express.

I think i finally fixed this method issues for both: streams with size and without size

Great! Feel free to make a PR and I'd be glad to have it implemented.

from hyper-express.