| commit | dd37316ba5fc2a2003ce4e6fae8910f64e92aaac | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Fri Nov 17 12:53:31 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 17 12:54:18 2023 -0800 |
| tree | 4406a78bdb478559920c310131e90fe5d14154c9 | |
| parent | fabe05f280e19ecd06bf34588239d42606026471 [diff] |
Flush buffered decoder stream data in qpack_round_trip_fuzzer. EncodingEndpoint destructor CHECKs that all references have been acknowledged. This condition was violated since decoder stream data was delayed at cl/557313748 and cl/582131467. Changing the fuzzing engine to FuzzTests covered this issue, because it flips flags by default when fuzzing. This change allows FuzzTest to be turned back on for qpack_round_trip_fuzzer. Startblock: * BTRGuardian allows cl/583126309 PiperOrigin-RevId: 583465270
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.