roll: third_party/pigweed Revert "pw_grpc: Fail Explicitly on Unsupported HPACK Features" This reverts commit 9bc226447fb0561fb0233bc82a85b0224c78b4fb. Reason for revert: This uncovers the client side implementation error that it has a race with server settings change Failure Link: b/529510406 Original change's description: > pw_grpc: Fail Explicitly on Unsupported HPACK Features > > Modify the HPACK parser and connection handler to fail loudly (with > COMPRESSION_ERROR via GOAWAY) when a client attempts to use HPACK > dynamic table indexing or dynamic table size updates > 0, since our > server is stateless and advertises a dynamic table size of 0. > > Specifically: > - Reject indexed header fields with index > 61 (RFC 7541 §6.1). > - Reject literal header fields with name index > 61 (RFC 7541 §6.2). > - Reject dynamic table size updates > 0 (RFC 7541 §6.3). > - Send GOAWAY with COMPRESSION_ERROR on these failures. > > Original-Bug: 513566128 > Test: Unit test and manual test > Change-Id: I879a756b97655b85ed3602c50d3ed1cdd00f914d > Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/412056 # Not skipping CQ checks because original CL landed > 1 day ago. Original-Bug: 513566128 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/430854 Original-Revision: ef4e131f113a657a36539498cc499fbe04512cec Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 2b3947b60a0fff..ef4e131f113a65 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8677584584328750305 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I717bf43276e5e6dc94f410593aaa586f25e51435 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/430952
This repository outlines the recommended way of using Pigweed in a new or existing project. Feel free to fork this repository, or read it as a reference.
For more information see the Pigweed Getting started guide.
Check back for more complex examples and features coming soon!
Make sure you've set up Pigweed's prerequisites.
If you're on Windows, you can automate the initial setup by downloading the first-time setup script from cmd.exe:
curl https://pigweed.googlesource.com/pigweed/examples/+/main/tools/setup_windows_prerequisites.bat?format=TEXT > setup_pigweed_prerequisites.b64 && certutil -decode -f setup_pigweed_prerequisites.b64 setup_pigweed_prerequisites.bat && del setup_pigweed_prerequisites.b64
Then you can run the script with the following command in cmd.exe:
setup_pigweed_prerequisites.bat
Note: You may see a few UAC prompts as the script installs Git, Python, and enables developer mode.
Once that is done, you can clone this project with the following command:
git clone https://pigweed.googlesource.com/pigweed/examples
Pigweed uses a local development environment for most of its tools. This means tools are not installed to your machine, and are instead stored in a directory inside your project (Note: git ignores this directory). The tools are temporarily added to the PATH of the current shell session.
To make sure the latest tooling has been fetched and set up, run the bootstrap command for your operating system:
Windows
bootstrap.bat
Linux & Mac
source ./bootstrap.sh
After tooling updates, you might need to run bootstrap again to ensure the latest tools.
After the initial bootstrap, you can use use the activate scripts to configure the current shell for development without doing a full update.
Windows
activate.bat
Linux & Mac
source ./activate.sh
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
When you pull latest repository changes, run bootstrap:
source ./bootstrap.sh
If you're just launching a new shell session, you can activate instead:
source ./activate.sh
and rebuild with:
pw build
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.