| commit | 17b9f37ea501b1aff6541cd59be841e77de964ec | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Sat Mar 23 10:14:17 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Sat Mar 23 10:15:14 2024 -0700 |
| tree | a9e9cd3b45f28b137125bb7bfdbf851f4b3e8456 | |
| parent | 5a5081c2cfeea7d7a68558fec74121be2abbca9a [diff] |
Fix 15 ProtobufTransformer findings:
* Upgrade to the latest edition (15 times)
* See go/editions for more information about this migration.
* Based on blaze dependency analysis, these protos were found to only used in languages known to support editions.* If this proto is later required in a language that doesn't support editions yet, a pure rollback is safe and recommended.
See go/protobuf-edition-zero-lsc for more information on why you've received this change and why it is important.
This CL looks good? Just LGTM and Approve it!
This CL doesn’t look good? This is what you can do:
* Revert this CL, by replying "REVERT: <provide reason>"
* File a bug under go/protobuf-transformer-issue for category ProtobufTransformer if there's an issue with the CL content.
* File a bug under go/rosie-bug if there's an issue with how the CL was managed.
* For all other issues such as the formatting of the CL, please file a bug under
go/clrobot-bug.
* Revert this CL and not get a CL that cleans up these paths in the future by
replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
opt out the respective paths in your CL Robot configuration instead:
go/clrobot-opt-out.
This CL was generated by CL Robot - a tool that cleans up code findings
(go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/METADATA by
following go/clrobot#how-to-opt-in. Anything wrong with the signup? File a bug
at go/clrobot-bug.
#codehealth
Tested:
Local presubmit tests passed.
PiperOrigin-RevId: 618466227
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.