vinzenz/hyperhive
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: correct stale recv_blocking + vacuum references

Browse source
This commit is contained in:
damocles 2026-05-20 11:54:14 +02:00 • committed by Mara
parent c15eb85085
commit 44c86b9278
4 changed files with 10 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
hive-c0re/src/dashboard_events.rs
View file

@ -16,7 +16,7 @@
//! and re-emits each `MessageEvent` as a `DashboardEvent::Sent` /
//! `DashboardEvent::Delivered` with a freshly-stamped seq. Keeping the
//! broker's intra-process channel separate avoids coupling the broker
//! (used by `recv_blocking` inside the harness loop) to dashboard
//! (used by `recv_blocking_batch` inside the harness loop) to dashboard
//! presentation concerns.
//!
//! New mutation kinds (approval added/resolved, question added/answered,

9
hive-c0re/src/main.rs
View file

@ -148,9 +148,10 @@ async fn main() -> Result<()> {
tokio::spawn(async move {
forge::ensure_all().await;
});
// Periodic broker vacuum: drop delivered messages older than
// 30 days. Undelivered messages are always kept (still in
// flight). Runs hourly; first sweep happens immediately.
// Periodic broker vacuum: drop fully-acked messages older
// than 30 days. Delivered-but-unacked rows (recoverable via
// requeue_inflight) and undelivered rows are always kept.
// Runs hourly; first sweep happens immediately.
let vacuum_coord = coord.clone();
tokio::spawn(async move {
let interval_secs = 3600u64;
@ -178,7 +179,7 @@ async fn main() -> Result<()> {
// channel with a freshly-stamped seq, so the dashboard SSE
// sees broker messages + future mutation events on one
// stream with one monotonic seq. The broker's intra-process
// channel (used by `recv_blocking`) stays untouched.
// channel (used by `recv_blocking_batch`) stays untouched.
spawn_broker_to_dashboard_forwarder(coord.clone());
let dash_coord = coord.clone();
tokio::spawn(async move {