Mihail Stoykov

Maybe connected (although with ASCII strings so :man_shrugging: ) we had this panic but we can't reproduce it or find out what made it and unfortunately, the stacktrace is ......

@cemremengu I don't think @dop251 was cold or that they are unopen to contribution. As far as I can see this is the usual open-source project problem - contributions should...

First I am more against the change than for it - mostly because the benefit is not so big and the downside is that we will have to have another...

that is a good solution or we can have another configuration in the config that is where the static files are. But for me this is the best and the...

relevant golang [issue](https://github.com/golang/go/issues/1435)

the proposed workaround in the upstream bug will work for us as well. We actually do half of it even now with the facebook's grace

This will more or less require types.App to be provided to each handler when it's created in New. This is probably not a bad idea as it will mean that...

So the scenario is : 1. cache (module) is asked for a file. 2. we have the first 2 parts of the file and we return them from the storage...

Probably a connected case: for a file with 100 pieces the following piece ranges have been cached: 10-20, 25-35 and 40-45. A request for pieces 10-45 comes in but pieces...

The second part (actually making websocket requests) should probably wait for an async websocket support in k6