Google Git
Sign in
pigweed / pigweed / examples / 4035afb89adae79d317c738e07eac520fbc884a1
commit4035afb89adae79d317c738e07eac520fbc884a1[log] [tgz]
authorAlexei Frolov <frolv@pigweed.infra.roller.google.com>Thu Sep 12 18:48:15 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Sep 12 18:48:15 2024 +0000
tree6ec1c5ecd3bbdb34c9613a412189d9b4a3114ce1
parent0a246bcc2dbb7b5e057cdfa0e0f9c4bcf6c4529d [diff]
roll: third_party/pigweed: pw_transfer: Send continue parameters for already recevied chunks

This changes the behavior of pw_transfer when a receiver receives a
chunk of data it already has. Instead of entering the recovery state,
slashing its window size, and requesting an immediate retransmission,
it instead simply sends a PARAMETERS_CONTINUE chunk with its current
offset and window end offset.

This is done to minimize back-and-forth between the transfer peers by
not automatically invalidating any in-flight packets, in case the
expected packet is already on the way.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/235100

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 382fb9839456b21..2496aee1a4ab3d9
Roller-URL: https://ci.chromium.org/b/8736977259469858353
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I63f3d2dabc9796e59d7285dceadc8a52447fa899
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/235472
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 6ec1c5ecd3bbdb34c9613a412189d9b4a3114ce1
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .clang-format ⇨ third_party/pigweed/.clang-format
  11. activate.sh ⇨ bootstrap.sh
  12. .bazelignore
  13. .bazelrc
  14. .bazelversion
  15. .gitattributes
  16. .gitignore
  17. .gitmodules
  18. .gn
  19. .pw_console.yaml
  20. activate.bat
  21. banner.txt
  22. bootstrap.bat
  23. bootstrap.sh
  24. BUILD.bazel
  25. BUILD.gn
  26. BUILDCONFIG.gn
  27. LICENSE
  28. MODULE.bazel
  29. navbar.md
  30. OWNERS
  31. pigweed.json
  32. pyproject.toml
  33. README.md
README.md

Pigweed Sample Project

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!

Getting started

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

Environment setup

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

Building

All of these commands must be run from inside an activated developer environment. See Environment setup

One-shot build

To build the project, documentation, and tests, run the following command in an activated environment:

pw build

Automatically build on file save

Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:

pw watch

Typical workflow

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

More info and Examples

Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.