Kartik

@tjzel I see, I guess this problem is just very hard to recreate? because the thing is If It was subtle enough that other people may not see it, then...

Hey @tjzel I know this issue is stale at the moment due to a lack of your anyone on the team's response to the above. But If anyone else encounters...

I see, I'll begin to look into this further but It seems to be a bug which would have to do with backpressure handling. The problem is I can't seem...

Yes, the `offset` argument comes from `uWebsockets.js` as it is supposed to tell you how many bytes of the original chunk were written. At least that is how I understand...

> Could this be related? [uNetworking/uWebSockets.js#726 (comment)](https://github.com/uNetworking/uWebSockets.js/issues/726#issuecomment-1083081077) That would explain it actually, so we shouldn't use the `offset` from the `onWritable` callback since the `write` call will buffer and write...

> I have the same question! > > I guess at this point when backpressure happens, the only thing we need to handle is to just wait for the `drain`...

No, you cannot use `.end()` since `.end()` is meant to be the final call to end the response. When there is a `total_size` provided, we have to use `tryEnd`. Why...

> If that's the case I think the simplest solution would be to `resolve` the promise and early return when `total_size` is not provided. We already have a condition we...

This bug has been fixed in the recent `v6.17.1` update of `hyper-express` which is now live. @amir-s Apologize for the long delay, was extremely busy with work so was unable...

Seems like we would need a setter here which can act as a setter on the internal url cache property. Do you think you could make a PR which would...