roll: pigweed Revert "pw_tokenizer: Never silently detokenize collisions in Python" This reverts commit 8bbf38974855143e72c88b5ac43f2c65f04caabd. Reason for revert: Need to handle intentionally corrupt decodes in snapshot (dropped arguments); likely in decode_optionally_tokenized Original-Bug: b/416030128 Original change's description: > pw_tokenizer: Never silently detokenize collisions in Python > > To avoid misrepresenting messages, nested messages should only be > decoded if they are unambiguous -- only one successful way to decode > them. > > The Python nested detokenization code was accidentally checking > .matches() (the list of possible matches) instead of .ok(). This > evaluated true for any positive number of matches, which could silently > result in an ambiguous decode. This commit updates nested Base64 > decoding to only decode unambiguous matches. > > Original-Bug: b/416030128 > Change-Id: I24a7bc166484564908377a92a9d3fbd02f35c0d4 > Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289452 > Reviewed-by: Armando Montanez <amontanez@google.com> > Docs-Not-Needed: Wyatt Hepler <hepler@google.com> > Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> > Commit-Queue: Wyatt Hepler <hepler@google.com> > Pigweed-Auto-Submit: Wyatt Hepler <hepler@google.com> TBR=hepler@google.com,amontanez@google.com,pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,android-build-ayeaye@system.gserviceaccount.com Original-Bug: b/416030128 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289632 Original-Revision: 435f8ca9a58e9bff5e703fa52ea1519617b6749c Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 68343a011dd40d..435f8ca9a58e9b Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8715474388027528769 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia44ccb47de2494b98781085897eceabee31d6b82 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/289579 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.
git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart cd pw_bazel_quickstart
The only dependency that must be installed is Bazelisk.
Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.
Instructions for installing Bazelisk can be found here.
To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console
To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.
To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console
Once connected with a console, RPCs can be sent to control the LED. Try running:
device.set_led(True) device.set_led(False) device.toggle_led() device.blink(blink_count=3)
bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.
bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.
Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.