J. Nick Koston fa17215053 Address review: fan-out guard, refusal warning, sighting-less connect hint ...

- The connected fan-out stops if a node tears the link down mid-loop
  (latent until a backend settles a teardown synchronously)
- A synchronously refused disconnect logs its own warning - a backend/
  client state divergence is no longer the most quietly logged outcome
- An action-initiated connect before any sighting warns that the public
  address type is assumed (an opaque repeated failure becomes
  self-diagnosing); the connect() doc no longer mentions a config key
  that does not exist
- The explicit-connections ledger test asserts the exact charged count;
  the host-test override comment names the current gate macro

2026-08-09 10:43:21 -05:00

..

__init__.py

[bluetooth_proxy] Platform-neutral advertisement proxy via ble_device_base (#17880)

2026-08-05 15:06:01 -05:00

test_idf_max_connections_mirror.py

[bluetooth_proxy] Enable active connections on rp2 (#18132)

2026-08-07 13:51:41 -05:00

test_outer_schema_mirror.py

Name the platform explicitly in schema builders for the dumper

2026-08-09 01:01:21 -05:00

test_platform_gates.py

Address review: fan-out guard, refusal warning, sighting-less connect hint

2026-08-09 10:43:21 -05:00