[MacOS Bug] unitree-g1-nav-sim fails to start due to invalid simulation=True config
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- robotics, testing-qa
Research direction
Start at dimos/robot/unitree/g1/blueprints/navigation/unitree_g1_nav_sim.py:88 and inspect the GlobalConfig.simulation type. Run uv run dimos run unitree-g1-nav-sim to reproduce the validation failure, then add or update the blueprint startup test mentioned in the issue. Done means the blueprint builds and starts without the simulation configuration error.
Written by the indexing model from the issue text.
Description
Description
unitree-g1-nav-sim fails during blueprint construction because it sets simulation=True, while GlobalConfig.simulation expects a string.
Environment
- DimOS:
v0.0.14b1 - macOS: 26.4.1
- Architecture: Apple Silicon (
arm64) - Python: 3.12.13
Steps to reproduce
uv run dimos run unitree-g1-nav-sim
Actual behavior
The blueprint fails during startup with:
ValidationError: 1 validation error for GlobalConfig
simulation
Input should be a valid string
input_value=True
input_type=bool
The traceback shows the failure occurs while applying blueprint global config during:
ModuleCoordinator.build(...)
global_config.update(...)
Root cause
The blueprint currently contains:
.global_config(n_workers=8, robot_model="unitree_g1", simulation=True)
at:
dimos/robot/unitree/g1/blueprints/navigation/unitree_g1_nav_sim.py:88
GlobalConfig.simulation expects a string rather than a boolean.
Expected behavior
unitree-g1-nav-sim should build successfully and start the simulation without a config validation error.
Suggested fix
Update the blueprint to pass the expected string value for simulation instead of:
simulation=True
and add/update a blueprint startup test so this config mismatch is caught automatically.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 224
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.
More from dimensionalOS/dimos
-
bug mac
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dimensionalOS/dimos#4134 ·
-
bug rust
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dimensionalOS/dimos#4055 ·
-
bug install
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dimensionalOS/dimos#3971 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
dimensionalOS/dimos#3898 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
dimensionalOS/dimos#3851 · 1 comment ·
All issues in dimensionalOS/dimos
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100