Ricardo Lanziano
Ricardo Lanziano
FWIW I've been sending Erlang terms from current AtomVM `master` using this branch to OTP 26.x applications without any issue when it comes to atom encoding.
Using `no_ack: true` in the options has no effect: I see no connected consumers in RabbitMQ and I see a lot of stalled messages, but I also see that data...
Sorry for the delay. I am going to try to get `no_ack: true` to work in the afternoon. I haven't tried it further because we are ACK'ing in production so...
@UncleGrumpy @petermm this only happened to me during that session and haven't seen that log warning again, but I agree that instead of `event 21` a possible `ESP_ERR_WIFI_NOT_ASSOC` would be...
Yes, given you have Erlang/OTP and rebar3.
FWIW, I'm also hitting this error using gitea with the same fly.io template and `ubuntu-latest`. Works fine if I use `ubuntu-22.04`