Skip to content

feat: add --no-ui flag for headless runs - #35

Merged
3Hren merged 1 commit into
masterfrom
feat/no-ui
Jul 26, 2026
Merged

3Hren merged 1 commit into
masterfrom
feat/no-ui

Conversation

@3Hren

@3Hren 3Hren commented Jul 26, 2026

Copy link
Copy Markdown
Member

Add a global --no-ui flag that runs the generator without the interactive TUI.

In headless mode the in-process gRPC seam (whose only client is the TUI) is not stood up at all, and graceful shutdown is driven by SIGINT (Ctrl-C) or SIGTERM instead of the UI loop: the signal flips is_running, draining the engine and the generator loop exactly as if the TUI had exited. The run also ends on load-profile exhaustion, as before.

The Prometheus API server (--api-addr) keeps working unchanged, so headless runs remain observable. This suits scripted runs, CI, containers and remote sessions where a terminal UI is unwanted or unavailable.

Verified manually: dwd udp 127.0.0.1:9 --no-ui --api-addr 127.0.0.1:18099 serves metrics and exits 0 on both SIGINT and SIGTERM; the TUI path is untouched apart from moving into the non-headless branch.

Add a global --no-ui flag that runs the generator without the interactive
TUI. In headless mode the in-process gRPC seam (whose only client is the
TUI) is not stood up at all, and graceful shutdown is driven by SIGINT
(Ctrl-C) or SIGTERM instead of the UI loop: the signal flips is_running,
draining the engine and the generator loop exactly as if the TUI had
exited. The run also ends on load-profile exhaustion, as before.

The Prometheus API server (--api-addr) keeps working unchanged, so
headless runs remain observable. This suits scripted runs, CI, containers
and remote sessions where a terminal UI is unwanted or unavailable.
@3Hren
3Hren merged commit c787713 into master Jul 26, 2026
8 checks passed
@3Hren
3Hren deleted the feat/no-ui branch July 26, 2026 15:20
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