roll: third_party/pigweed pw_bluetooth_sapphire: Set L2CAP opened centrally
DynamicChannel::opened_ was set manually by each channel type before
invoking the open callback, so any path that delivered an open channel
without calling set_opened() (as the BR/EDR inconsistent-mode Basic
fallback did before 2aabcf247) caused remote disconnects to skip
close_cb_ and leak the channel.
Mark the channel opened in DynamicChannelRegistry at the single point
where an open channel is handed to the caller, and make set_opened()
private so channel implementations can no longer get out of sync.
Original-Bug: b/525194018
Test: bazelisk test --config=googletest \
//pw_bluetooth_sapphire/host/l2cap:l2cap_test \
//pw_bluetooth_sapphire/host/gap:gap_test \
//pw_bluetooth_sapphire/host/sdp:sdp_test \
//pw_bluetooth_sapphire/host/testing:all
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/500893
Original-Revision: 06cf2cf0cb4d5cf40f1aa46bdb254744f8c3f1ce
Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 4a96b36dad6baf..06cf2cf0cb4d5c
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8668045552392821185
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I685bbbbfcc09b5f6bf223ef0789ed25d41318011
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/501394
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.