alyssawilk

Oh nice, this one has the details of what needs to be done. Thanks for filing it @goaway and digging it up, @junr03

SGTM. We'll see if we can figure out how to test it over on our side of things then :-)

OK, I'm working on a PR to wire up the error flags. Once we do that I think we can track most of these. @RyanTheOptimist I'd like your thoughts on...

For ERROR_QUIC_PROTOCOL_FAILED would it make sense to either convert known errors (connection failure etc) to ERROR_QUIC_PROTOCOL_FAILED when we've negotiated HTTP/3, or use it instead of ERROR_OTHER when HTTP/3 is in...

@colibie SG, on it.

And done, thanks for your patience :-)

Wohoo! Thanks so much for all your work on this!

@DavidSchinazi when you're back, this feels like a space where I (who know Envoy errors) could collaborate with Renjie (who knows Chrome ones) to do a mapping of sorts?

I suspect that's an artifact of the old error pathways that @goaway has mentioned. Upstream reset should be communicated with the UpstreamRemoteReset flag is set and EarlyUpstreamReset/LateUpstreamReset details, which can...

cc @envoyproxy/envoy-mobile-triage I think this is flaky test rather than ci - can someone at lyft confirm and look into debugging?