Enable Popcorn on vanilla AtomVM
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- erlang
- Domain
- backend
Research direction
The issue lists AtomVM features needed to run Popcorn, with related work tracked in issues #2186–#2195, #2013, #2359, #2157, and #2027. Start by checking the status of those linked issues and identifying any remaining requirements. The issue does not specify a concrete change or completion criteria beyond enabling Popcorn on vanilla AtomVM.
Written by the indexing model from the issue text.
Description
Following issues must be addressed in order to run Popcorn on vanilla AtomVM:
binary_split/2,3- Fission's version supports a list of patterns (#2186) andtrimandtrim_alloptions (#2187), AtomVM doesn'tcode:get_object_code- see #1814erts_internal:cmp_term/2- this is private BEAM API but it is needed (#2188)shortoption forerlang:float_to_list- Popcorn needs it but it's hard to implement, Popcorn has a workaround (#2189)process_info/1(#2190), list of options forprocess_info/2(#2191),trap_exitkey inprocess_info/2(#2192) - there's a PR for that to fission, can be upstreamed,A mockednode/1, BIF that always returns the current node (#2195)erlang:display_string(#2193) - missing in AtomVM, can be upstreamed,Improved JS interop - see #2013 / #2359New ETS - see #2157Process aliases - see #2027
- Dominant language
- Erlang
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 atomvm/AtomVM
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
lwIP sockets: a failed listen or connect leaves the socket lock held, a later close hangs foreverOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 3 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
milind-soni/OpenMausBot#5829 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
finos/fluxnova-bpm-platform#387 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
OHDSI/Data2Evidence#3693 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Project-N-E-K-O/N.E.K.O#3725 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
kubernetes-sigs/headlamp#8408 ·
Maintainers usually reply within 1 day