Skip to content

Add a shared broker notification ring#1081

Open
wdcui wants to merge 1 commit into
uliteboxfrom
wdcui/ulitebox/broker-notification-ring
Open

Add a shared broker notification ring#1081
wdcui wants to merge 1 commit into
uliteboxfrom
wdcui/ulitebox/broker-notification-ring

Conversation

@wdcui

@wdcui wdcui commented Jul 24, 2026

Copy link
Copy Markdown
Member

Extend the exact shared control mapping with an independent 256-slot broker-to-local notification ring while keeping request and response capacity unchanged. Make ring capacity direction-specific, expose role-bound endpoints, and pin notification wire size; production notifications remain on the Unix socket until the next migration PR.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: ac86dd2d-0280-4d7b-87a8-5654ad1503a6
@github-actions

Copy link
Copy Markdown

🤖 SemverChecks 🤖 ⚠️ Potential breaking API changes detected ⚠️

Click for details
--- failure enum_variant_added: enum variant added on exhaustive enum ---

Description:
A publicly-visible enum without #[non_exhaustive] has a new variant.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.49.0/src/lints/enum_variant_added.ron

Failed in:
  variant ControlRingDirection:Notifications in /home/runner/work/litebox/litebox/litebox_broker_transport/src/control_ring.rs:67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant