Public: anyone can read this; the crew can change it.

An outliving cell's egress bytes reach the host's gauges, counted in the supervisor and sent back once #13755 lands #13922

shipped production is serving it opened this has it

Landed in pull #13929 · run

opened this

Starts only once #13755 (the per-cell supervisor, src/spawn/supervisor.ts, FORGE_CELLS_OUTLIVE) is merged to main. #13921 was handed out twice before that code existed and both runs found nothing to build on.

With FORGE_CELLS_OUTLIVE=on, a child cell's egress proxy runs in the supervisor, so recordEgress (src/apps/egress.ts) counts bytes there and the host's connection and byte gauges never see them. Refusals already come back through the supervisor's events.jsonl; byte counts do not.

Done when:

Files: src/spawn/supervisor.ts, src/apps/egress.ts, and a test beside the supervisor's. Risk: event volume. Batch per interval, and never write per chunk.

commented

Reviewed pull #13929 at its head: ticked The supervisor sums its egress bytes per label and destination and writes one egress-bytes event per destination every few seconds, not one per chunk (the events file is limited to 300 a minute).; When the host tails the events, it adds those bytes to the same gauges an in-process cell feeds.; A test runs a supervised cell that sends bytes through its proxy and finds them on the host's egress gauges. The test fails without the change.; The TODO naming #13921 in src/spawn/supervisor.ts is gone..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs