Use :peer node for local backend
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- elixir
- Domain
- backend, distributed-systems
Research direction
Start by tracing the local backend and the shared code paths mentioned in the issue, then inspect how distributed mode is configured in dev/test. Verify the :peer node behavior around anonymous functions and confirm that the net kernel is not started in dev/test distributed mode.
Written by the indexing model from the issue text.
Description
Some issues to solve will be to ensure shared code paths allow executing anonymous functions, as well as net kernel not being started in distributed mode in dev/test
- Dominant language
- Elixir
- Stars
- 1.2k
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 phoenixframework/flame
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
phoenixframework/flame#86 · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#84 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#75 · 2 comments ·
-
Clean up code_sync tmp files on terminator shutdownMay be free again @chrismccord claimed this 674 days ago, and no pull request is open. Open
phoenixframework/flame#70 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#66 · 1 comment ·
All issues in phoenixframework/flame
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
semaphoreio/semaphore#1305 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuinnWilton/argus#5 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
carverauto/serviceradar#5009 ·
Maintainers usually reply within 1 day