Alessandro Ghedini

The way I've been running this is something like `memleak --obj /path/to/binary` and once the probes are attached I actually run `/path/to/binary`. In order to avoid breaking previous use cases...

@AGWA Is there any news on this? I haven't tried your patch yet (merge conflicts), but let me know if any testing/help is needed. It'd be nice to have an...

No, that is not possible currently due to symbols conflicts between BoringSSL and OpenSSL (as per the logs you posted).

To answer your original question, Wireshark should definitely be able to decode QUIC v1 packets, though you might need a recent version (according to https://github.com/quicwg/base-drafts/wiki/Tools#wireshark you need at least v3.4.x).

As for the `STREAM_DATA_BLOCKED` thing, it does indeed look weird, Are you using a custom client/server or the apps we provide (https://github.com/cloudflare/quiche/tree/master/tools/apps)? If the latter, it would be useful if...

Yeah, that seems like something that could be useful, thanks.

Also needs rebase plz.

Let's be clear here though. The point of this PR is to fix a problem with the existing and currently used flow control update mechanism, the point is _not_ to...

Not yet, but it is planned.

We don't really support network migration yet (e.g. we don't probe/validate new paths), but in your specific case I think there might be something else going on with your application,...