Elixir v1.15.0 released

I assumed it was a log with level :warn sneaking in somewhere but no, the problem is different. I am still trying to pinpoint what’s going on, but the issue disappears completely with --max-cases=1, and then gradually starts to show up as I increase the concurrency of tests. At --max-cases=6 it’s almost always guaranteed to happen in my test suite.

Edit: I opened a bug report here: ExUnit.CaptureLog fails in tests on high concurrency · Issue #12692 · elixir-lang/elixir · GitHub we can move conversation there

Thank you for testing it.

I found that the issue is probably connected to fun_with_flags, specifically when runtime: false is used. It works with Elixir 1.14.5-otp-26.

I was able to replicate a minimal app that causes the issue:

mix new ek --sup --module EK

and then use the following mix.exs as is:

defmodule EK.MixProject do
  use Mix.Project

  def project do
    [
      app: :ek,
      version: "0.1.0",
      elixir: "~> 1.15",
      start_permanent: Mix.env() == :prod,
      deps: deps(),
      releases: [
        ek: [
          include_erts: true,
          include_executables_for: [:unix],
          applications: [
            ek: :permanent,
            fun_with_flags: :load
          ]
        ]
      ]
    ]
  end

  # Run "mix help compile.app" to learn about applications.
  def application do
    [
      extra_applications: [:logger],
      mod: {EK.Application, []}
    ]
  end

  # Run "mix help deps" to learn about dependencies.
  defp deps do
    [
      {:ecto_sql, "~> 3.6"},
      {:postgrex, ">= 0.0.0"},
      {:fun_with_flags, "~> 1.10.1", runtime: false}
    ]
  end
end

❯ mix release ek
Generated ek app
** (Mix) Could not find application :myxql

I am now trying to figure out what’s wrong

Can you please open up an issue with pretty much what you have here? So I don’t forget about it and then I can investigate it as soon as possible. Thank you!

Thank you @josevalim v1.15.0: Unable to assemble the release - optional dependencies (applications) are missing · Issue #12694 · elixir-lang/elixir · GitHub

I was unable to determine on which side the problem might be.

I just tried the new version today.

First issue as other mentioned before, ssl_verify_fun broken and need to be updated.

Several surprising differences so far was formatting.

• mix format default line_length constraint becoming exactly 98 as docs said (previously it was 100 somehow), so running mix format --check-formatted on existing code will be failed until we reformat (if we accidentally have lines with 100 chars length).
• typespec for anonymous function replaced with empty string by formatter, ie

  @spec proces_fn((() -> term()), keyword()) :: term()
  

  will be replaced to

   @spec proces_fn(( -> term()), keyword()) :: term()
  

  Dialyzer works as expected, just feel a bit strange for me at first.
• charlist written inside ' replaced with sigil ~c"" i.e 'word' become ~c"word"

I’ve checked the changelog, they’re already documented. So. no issues so far.

Thanks for the update!

I have noticed a small but annoying “but”:

➜ does anyone else find the new behavior of reporting multiple errors per file a bit tedious?

I find myself scrolling around a lot now,
in need to find the actual error embedded within the other warnings - as the last message is not always the actual error anymore.

It breaks my workflow so heavily (code reloading in Phoenix and seeing errors in the browser or doing recompile() in iex) that I reverted to 1.14 for now.

Is there maybe an option to re-enable the old behavior again?

You should be able to see errors in the Phoenix error page. Make sure you are on latest and, if it still does not work, please let me know.

The error shows but in a different spot than before. Let me explain in detail.

If there are yet unsolved warnings (which one want to take care of later)
it makes it hard to glance in an instance what the error is you just introduced in your code.

Browser1200×593 59.4 KB

Also, in iex, this is different than before:

Terminal1200×578 78.5 KB

The screenshots I chose have the number of warnings fit the screen, but I might have more of them.
I even think I saw an error once in the middle of the list of warnings.

➜ for terminal & browser that leads to scrolling around where the error is, which takes time and involves mousing.

• in iex: it would be ideal to have the warnings first, error(s) last.
• in phoenix error pages: error(s) first, warnings after

it was like this till 1.14

I could also live with hiding warnings in iex and Phoenix at all, as I mostly need them for elixir-ls anyway - but that seems also wrong to me.

I hope I don’t come around as nitpicky, but these details are important for developer experience, and error handling in elixir is known to be good.

That’s a consequence of parallel compilation. We indeed may have warnings from other files overlapping. We will see how to improve it, we should at least hide the shutdown message, but the new behavior is somewhat expected.

But also, if that is motivation to fix warnings, even better.

I’m seeing this error when running dialyzer with Dialyzer v5.1 Elixir 1.15 OTP 26

** (UndefinedFunctionError) function Dialyxir.Output.info/1 is undefined (module Dialyxir.Output is not available)
    (dialyxir 1.3.0) Dialyxir.Output.info("Finding suitable PLTs")
    (dialyxir 1.3.0) lib/mix/tasks/dialyzer.ex:172: Mix.Tasks.Dialyzer.run/1
    (mix 1.15.0) lib/mix/task.ex:447: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.15.0) lib/mix/cli.ex:92: Mix.CLI.run_task/2

I guess that means Dialyxir isn’t fully loaded? This was working with Elixir v1.14.