Skip to content

brw v0.5.2 — extension-connection flap guard

Choose a tag to compare

View all tags
@revitteth revitteth released this 01 Jul 09:51
v0.5.2
This tag was signed with the committer’s verified signature.
revitteth Max Revitt
SSH Key Fingerprint: hSu0lwdvgGmc075P3libkV/1P37R7Y51dFjU4RAiWr4
Verified
Learn about vigilant mode.
ef5262b
This commit was signed with the committer’s verified signature.
revitteth Max Revitt
SSH Key Fingerprint: hSu0lwdvgGmc075P3libkV/1P37R7Y51dFjU4RAiWr4
Verified
Learn about vigilant mode.

brw v0.5.2 — extension-connection flap guard (fixes the flashing icon)

When two browser profiles run brw against the same bridge (e.g. Profile 1 and Profile 2 both have the extension enabled on the default port), the two extensions endlessly displaced each other — connected → "replaced by new extension connection" → disconnected, several times a second. That churn is the flashing brw icon, and it makes the bridge unusable.

  • The bridge now detects the flap (≥5 connection replacements within 10s) and enters a hold: it keeps the live connection and rejects intruders (StatusTryAgainLater) instead of replacing, extending the hold while collisions continue. A genuine single reconnect (MV3 service-worker restart, network blip) is unaffected — the hold only trips on rapid churn, and is bypassed the moment the live connection actually drops.
  • Result: the winning connection stays stable (icon steady), and the daemon logs an actionable hint naming the fix (disable brw in the other profile, or give it its own --bridge-addr).

Regression test: TestExtensionFlapGuardRejectsColliding.

Full changelog: v0.5.1...v0.5.2

Assets 10
Loading