Skip to content

Serve the run result from a read-only status server - #547

Closed
stephanos wants to merge 2 commits into
stephanos/omes-result-filefrom
stephanos/omes-result-status
Closed

stephanos wants to merge 2 commits into
stephanos/omes-result-filefrom
stephanos/omes-result-status

Conversation

@stephanos

@stephanos stephanos commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Stacked on #534 (result file on exit). Replaces #544, which rewrote the result file periodically while running; reading live progress over HTTP is simpler and needs no shared volume.

  • New --status-listen-address on run-scenario and run-scenario-with-worker (empty, the default, disables it) starts a small, separate HTTP server that serves GET /status.
  • /status returns the same JSON as the result file: outcome: "running" with current iteration counts and scenario state while the scenario runs, then the final result.
  • The runner starts the server before the scenario and shuts it down only after the final result is recorded, so the listener closes cleanly. A listen failure (e.g. address in use) fails the run early.
  • Read-only by design: starting and stopping a run stays with whatever runs the process (signals, container lifecycle).
  • Prometheus is untouched: --prom-listen-address and the metrics server behave exactly as before.
  • Works without --export-result-file; the file stays the durable final result.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@stephanos
stephanos added this pull request to stack #548 November 9, 2026 19:17
Prometheus and --prom-listen-address are unchanged. The runner starts the
status server before the scenario and shuts it down after the final result
is recorded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@stephanos stephanos changed the title Serve the run result over HTTP at /status Serve the run result from a read-only status server Nov 9, 2026
@stephanos
stephanos removed this pull request from stack #548 November 9, 2026 19:34
@stephanos

Copy link
Copy Markdown
Collaborator Author

Closing in favour of #544 (reopened): without remote control on the HTTP side, rewriting the result file at an interval is simpler and gives one artifact for live and final results.

@stephanos stephanos closed this Nov 9, 2026
@stephanos
stephanos deleted the stephanos/omes-result-status branch November 9, 2026 19:34
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