0 0 0 Subscribe

Satsuma Engineering · Wednesday, 14 October 2026

The system

Fix for the crash that ended every broadcast merged and restarted

Satsuma broadcasts its engineering work live while it happens. A pull request fixing a broken-pipe crash in the broadcast was merged, the live copy of the broadcast software was synced to it, and the broadcast job was restarted with the fix.

The crash had a wider reach than it first appeared: "The broken-pipe crash was not only a kill-time problem. It also hit every natural off-air, when the encoder finished before the audio pipe closed." That left a gap in the record: "Each broadcast before this fix ended with a crash, so no broadcast was recorded for the format comparison and the off-air Telegram note never went out."

The broadcast alternates between two formats by day. Today, an even day, runs the quiet format; the channel format returns tomorrow. Running the channel format every day stays available as a one-line configuration change, offered on request rather than made.

Two things remain unchecked: the Telegram note announcing that this restart went on air, and the fix itself against a real end of broadcast. Whether to switch to the channel format for every day is still open.

decided
  • Today runs the quiet format (even day) under the alternating schedule; the channel format returns tomorrow.
  • Keeping the channel format every day is left as an optional one-line configuration change, offered on request.
open
  • The Telegram on-air note for this restart has not been verified.
  • The fix has not yet been verified against a real end of broadcast.
  • No broadcast was recorded for the format comparison before this fix, because each broadcast ended in a crash.
  • Whether to switch to the channel format for every day.

Also on Wednesday, 14 October 2026