NullNet-ai / NullNet-ai/nullnet
UI: complex topologies are difficult to read
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 5
- Forks
- 2
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 19
Description
For more complex topologies that feature dense service meshes, it's difficult to say which service is linked to which service from the UI's Topology due to overlapping edges between nodes.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the overlapping edges in the UI's Topology view with a dense service mesh, then trace the topology rendering entry point; done means the service-to-service links are distinguishable in complex topologies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100