Skip to content

Follow every run of the server in an Execution tab - #19

Merged
kineticsystem merged 1 commit into
mainfrom
follow-runs
Oct 7, 2026
Merged

kineticsystem merged 1 commit into
mainfrom
follow-runs

Conversation

@kineticsystem

Copy link
Copy Markdown
Owner

The editor could follow only the runs it started itself, through the feedback of its own goal. A run started from StepIt UI or the gamepad couldn't be seen, nor could a run already going when the page opened.

Two tabs in the centre panel: Editor and Execution.

  • Execution shows the server's run, whoever started it: the tree as it runs, with each node's status.
  • A run started elsewhere marks the Execution tab with its name, with a blue dot while it runs, but never takes the editor away. Opened, the tab says "started elsewhere".
  • A run from the Run dialog opens the Execution tab and keeps Stop, as before. Only the editor's own runs can be stopped there.
  • Nothing has run yet: the tab says so.
  • Removed: the back arrow, "Back to the editor" and "Running X / Last run" buttons, which the tabs replace.

How:

  • The editor follows /stepit_server/execution (stepit-commander PR), through rosbridge, from the moment it loads, and reconnects every 3 s.
  • The topic is a setting under the Run dialog's Connection, next to the URL and the action; empty follows no topic.
  • Its own run is recognised by the run number in its first feedback. From then on, the snapshots give its statuses, so a run looks the same whoever started it.
  • The feedback stays as a fallback for servers that publish no run.
  • A run started elsewhere shows once no run of the editor is going; it never replaces one. The goal's result, not the topic, ends the editor's own run.

Tests: 146 pass, 13 of them new:

  • parsing the snapshots;
  • following the topic and reconnecting;
  • the store: an outside run, the next run replacing the last, the editor's own run recognised on the topic, its run kept until it ends, and the feedback fallback.

Checked in a browser on the rig, with fake motors:

  • a run started from the command line marks the tab without leaving the editor;
  • a page reloaded mid-run shows the running nodes at once and follows the run to "Succeeded";
  • a run from the Run dialog shows Stop, and stopping ends it as "Stopped".

Docs: README (Running a Tree on the Robot, and the topic format under Monitoring a Run from Another Server) and docs/ARCHITECTURE.md. docs/execution.png still shows the old header, with its back arrow, and needs a new screenshot.

🤖 Generated with Claude Code

The editor showed only the runs it started, from the feedback of its goal: a
run started elsewhere, e.g. from StepIt UI, could not be seen, nor a run
opened in its middle. The center panel now has two tabs, Editor and
Execution. The editor follows the topic on which StepIt Commander publishes
the whole run, /stepit_server/execution, from the moment it loads: a run
started elsewhere marks the Execution tab, with its name, without taking the
editor away. A run of this editor is told on the topic by its number, from
its first feedback, and keeps Stop; the feedback serves a server that
publishes no run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kineticsystem
kineticsystem merged commit 28f4135 into main Oct 7, 2026
2 checks passed
@kineticsystem
kineticsystem deleted the follow-runs branch October 7, 2026 11:38
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