| commit | 37ccee708f1994e9504cf561a1da77468fee4f8b | [log] [tgz] |
|---|---|---|
| author | Alexei Frolov <frolv@pigweed.infra.roller.google.com> | Fri Apr 26 18:14:30 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 26 18:14:30 2024 +0000 |
| tree | 01e5693e21362087e9141cdae42e550bca8c020a | |
| parent | 8c090a80f3cd8928420f99bec145a2c523e33f53 [diff] |
[roll third_party/pigweed] pw_transfer: Assume a minimum window size when reserving space A pw_transfer receiver estimates how much data the sender can fit in a chunk by trying to calculate the protobuf overhead of transfer metadata. On the first chunk of a transfer, this calculation is performed before a window size is set (as setting a window size requires a max chunk size), potentially resulting in a larger initial chunk size. This caused issues in the case of retries, as a retried chunk could advertise a smaller (correct) window size than the initial chunk, invalidating any in-flight data transmissions. This updates the code to assume a minimum window size of one chunk when making its initial overhead calculation. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/206890 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 2593707a02b0c21..87126e11b80d206 Roller-URL: https://ci.chromium.org/b/8749572266749188753 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8ddedeb1fb0c01013949c76e42413a58df16cb08 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/206910 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
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/sample_project/+/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/sample_project
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.