software-mansion / software-mansion/live-debugger
Support LiveDebugger in distributed environment
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 765
- Forks
- 29
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 2
Description
This issue came out when working on #728. LiveDebugger is working fine in single node-environment, but when you start adding new nodes with LiveView processes they won't be traced. This isn't usually done in development, so the priority is rather low, but it'd be nice if we added some basic support for this
We may want to use mnesia instead of ets since it has support for distributed envs
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 locating the ETS-backed state and tracing setup used by LiveDebugger, then examine how LiveView processes on added nodes are discovered. Compare whether Mnesia provides the distributed coordination needed. Done means LiveView processes running on additional nodes can be traced with basic LiveDebugger support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- devtools, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100