jjcarstens

jjcarstens

Nerves Core Team

I started investigating using the new versions with Nerves. I have found a few pieces that need a little more vetting and investigation. Follow along here and test yourself if able :wink:

There are various PR’s open that would be needed to support this:

Elixir 1.17

  • nerves_ssh#154

    • Required to start the IEx shell when SSH-ing to device
  • The vm.args.eex needs to adjust to use -run elixir start_cli

    • nerves_bootstrap#316 fixes the mix nerves.new
    • I’m unsure :elixir.start_cli is the right entry point. May need more investigation

OTP 27


Current problems

  • OTP 27 does not boot. The only logs I have right now (via UART) are ¬
size_object: matchstate term not allowed
[nbtty: terminating]
[    8.035300] watchdog: watchdog0: watchdog did not stop!
[    9.107671] reboot: Restarting system

Showing Posts 2 to 1

karlosmid

karlosmid

Hi! Here is scenario how we triggered this error:

  1. asdf .tool-versions was on otp-27 and elixir-1.17
  2. we have github actions ci that was run, cache was created
  3. in .tool-versions we downgraded to elixir 1.16 and otp-26
  4. mix test triggered locally this error
  5. we deleted deps and _build localy
  6. github actions job failed, because of cache
  7. we bumped cache folder name to something different, _v1, github actions passed.
fhunleth

fhunleth

Co-author of Nerves

I just wanted to update this thread that the issue posted here was fixed. The size_object: matchstate term not allowed error can happen when you run Elixir 1.17 compiled with OTP 27 on OTP 26. The assumption is that this somehow happened here.

Support for Elixir 1.17 and OTP 27 is getting really close to being released with Nerves. It seems to be working well and we hope to release soon.

14
Post #1
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews