dimensionalOS / dimensionalOS/dimos
Unitree: retry connection on failure, give up after 5 minutes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Summary
When the Unitree connection fails (e.g. robot unreachable, network hiccup), dimos should automatically retry the connection instead of failing immediately.
Desired behavior
- On connection failure, keep retrying with backoff
- Give up after 5 minutes of unsuccessful attempts
- Log each retry attempt so the user knows what's happening
- After the 5-minute timeout, fail with a clear error message
Motivation
Transient network issues or a robot that's still booting shouldn't require a full restart of the dimos process. A retry window gives the robot time to become available.
Synced from DIM-717 by summer
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
No file or test is named. Start by locating the Python code that handles Unitree connection failures, then trace the failure path and existing logging; done means retries use backoff, each attempt is logged, and unsuccessful connection attempts produce a clear error after five minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100