Lars Wikman

Okay, that's fair. I agree that literals are probably the way to go. But I think module attributes in the test suite would be beneficial to clarity and reduce the...

Hehe, I know so little about what I'm doing with Erlang right now. Really need to read up. From your description I thought this would work: ``` -module(init). -export([start/0]). start()...

Same thing for: ./native_implemented/otp/tests/lib/erlang/get_1/with_key_returns_value/init.erl

@gerhard I think this is probably the reason I need to run `mix phx.digest` manually to get JS/CSS updated as well. But I'll just mentioned that here so you know...

Then it connects to the dev database. mix test handles the MIX_ENV=test for me, as it usually does. So there is some adjustments around config or environment variables that need...

Hmm.. my starting point. I mean I would probably just run a local postgres and want to run: > mix deps.get > mix ecto.create > mix ecto.migrate > mix phx.server...

Have had a moment to try some of the stuff. `make test` works fine. But a very common use-case for me is running a part of the test-suite. Such as...

I'm on VSCode and I did install ElixirLS on my remote.. But hmm, I probably installed it on the server which runs my containers, not inside the containers.. Might work...

I think this reproduces the problem in a reasonable experimental way, a livebook: # Packmatic starvation ```elixir Mix.install([:packmatic, :kino, :kino_vega_lite]) alias VegaLite, as: Vl ``` ## Section ```elixir delay =...

Pasting a livebook in github is kinda weird :D