dimensionalOS / dimensionalOS/dimos
unitree-go2 replay does not respond to terminal interrupt/suspend shortcuts while Rerun is open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Description
What happened?
During Linux testing of DimOS v0.0.13, the foreground DimOS process does
not respond as expected to terminal signals while running the Go2 replay
with Rerun open.
Observed behavior:
Ctrl+Cdoes not stop the foreground DimOS process.Ctrl+Zdoes not suspend the foreground process.- The shell prompt does not return.
- Manually closing the Rerun viewer is required before the terminal becomes
usable / DimOS can finish exiting.
The replay itself otherwise runs successfully.
What did you expect?
Ctrl+C should gracefully terminate a foreground DimOS run and return
control to the shell.
The DimOS CLI documentation describes foreground execution as:
Foreground (Ctrl-C to stop)
The Rerun viewer should not have to be manually closed to regain control
of the terminal.
System
Ubuntu 24.04.4 LTS
Robot / Sim / Hardware
Go2 replay (go2_short)
No physical Go2 connected.
GPU: NVIDIA GeForce RTX 5060 Ti
Steps to reproduce
-
Checkout DimOS
v0.0.13. -
Run:
uv run dimos --replay run unitree-go2 -
Wait for DimOS and Rerun to initialize.
-
Confirm replay data is loading.
-
Return focus to the terminal that launched DimOS.
-
Press
Ctrl+C. -
Observe that the process does not exit and the shell prompt does not return.
-
Press
Ctrl+Z. -
Observe that the process is not suspended.
-
Manually close the Rerun viewer.
-
Observe that the terminal becomes usable / DimOS can finish exiting.
Environment
- Install method:
uv - DimOS:
v0.0.13 - Commit: [INSERT v0.0.13 COMMIT]
- Python:
3.12.3
Additional context
The same run also reports:
- Rerun Viewer:
v0.32.0-alpha.1 - Rerun SDK:
v0.32.0
That mismatch is being tracked separately. It has not been established
whether it causes this shutdown behavior.
Reproducibility
Reproduced across multiple Go2 replay runs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running uv run dimos --replay run unitree-go2 on Ubuntu and observe foreground behavior with Rerun open. Trace the CLI entry point and replay shutdown path for terminal signal handling. Done means Ctrl+C gracefully exits DimOS and returns the shell prompt without manually closing the Rerun viewer; Ctrl+Z should suspend the foreground process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100