Suchith J N

I think it is important to have this configurable. Unfortunately, something like `istioctl precheck` as mentioned in the blogpost is not applicable here as apps are blackboxes from Istio perspective....

Apparently, envoy can route if casing is not correct. Here is a small experiment I did to test that. docker-compose.yaml ```yaml version: '3' services: envoy: image: envoyproxy/envoy-dev:ae780e21824bcb947299f5a048797fbf3cac21ba ports: - "10000:10000"...

I'd like to give a shot. I have some parts like checking for stateless reset token implemented. But not yet polished/finished (and unit tests aren't there yet).

The protocol itself does not prevent it. You can have client/server initiated, uni/bi-directional streams within the same connection. Why not use multiple streams for this? This way you can multiplex...

Usually, download is where the remote would be sending lots of data and upload is where the local would be sending lots of data right? You can make use of...

I traced the root cause for this - It is because the buffer pool is global ```go var bufferPool sync.Pool ``` When the test "panic if released twice" is run,...

Related - https://github.com/lucas-clemente/quic-go/issues/3164

It is possible to refactor buffer into its own package (maybe move to internal/buffer). Then fix CI to run it separately. CI configs get tedious with this approach :( However,...

I agree. That's weird. If tests are not being run concurrently, then how is the race detector pointing to different tests [in different goroutines]? Here the stack trace clearly shows...