dimos --listen-host doesn't affect rerun
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- backend, networking
Research direction
The issue names no files or tests. Start by tracing how rerun binds its listener and compare that path with the websocket handling of listen-host; done means rerun listens on the configured host instead of always using 0.0.0.0.
Written by the indexing model from the issue text.
Description
rerun seems to always listen on 0.0.0.0 but websocket respects listen-host
- 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 mac
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dimensionalOS/dimos#3918 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
dimensionalOS/dimos#3898 · 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