dimensionalOS / dimensionalOS/dimos
Shared memory topic discoverability
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Rerun and the spy can't see topics published over shared memory, so anything on that path is invisible for debugging. Shared memory topics need to be discoverable the same way normal topics are, otherwise moving a stream to shared memory means giving up all observability of it.
Synced from DIM-1459 by jeff
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 tracing how Rerun and the spy discover normal topics, then compare that path with topics published over shared memory. Done means shared-memory topics appear in both tools with the same discoverability as normal topics, preserving observability when a stream uses that transport.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100