sodapopcan

sodapopcan

Wallaby with Phoenix 1.16.rc0

Has anyone successfully gotten Wallaby to work with Phoenix 1.16-rc.0?

It’s complaining that it can’t use mime:

Failed to use "mime" (version 2.0.1) because
  plug (version 1.12.1) requires ~> 1.0 or ~> 2.0
  swoosh (version 1.5.0) requires ~> 1.1 or ~> 2.0
  tesla (versions 1.3.0 to 1.3.3) requires ~> 1.0
  mix.lock specifies 2.0.1

** (Mix) Hex dependency resolution failed, change the version requirements
of your dependencies or unlock them (by using mix deps.update or mix deps.unlock).
If you are unable to resolve the conflicts you can try overriding with
{:dependency, "~> 1.0", override: true}

So, as suggested by the output, I add an override mime with:

defp deps do
  # ...
  {:mime, "~> 2.0.1", override: true},
  # ...
end

This leads to further complaints about telemetry (twice):

Failed to use "telemetry" (version 1.0.0) because
  cowboy_telemetry (version 0.4.0) requires ~> 1.0
  db_connection (version 2.4.0) requires ~> 0.4 or ~> 1.0
  ecto (version 3.7.1) requires ~> 0.4 or ~> 1.0
  ecto_sql (version 3.7.0) requires ~> 0.4.0 or ~> 1.0
  phoenix (version 1.6.0-rc.0) requires ~> 0.4 or ~> 1.0
  phoenix_live_view (version 0.16.3) requires ~> 0.4.2 or ~> 1.0
  plug (version 1.12.1) requires ~> 0.4.3 or ~> 1.0
  swoosh (version 1.5.0) requires ~> 0.4.2 or ~> 1.0
  telemetry_metrics (version 0.6.1) requires ~> 0.4 or ~> 1.0
  telemetry_poller (version 1.0.0) requires ~> 1.0
  tesla (versions 1.3.0 to 1.3.2) requires ~> 0.3
  mix.lock specifies 1.0.0


Failed to use "telemetry" (version 1.0.0) because
  cowboy_telemetry (version 0.4.0) requires ~> 1.0
  db_connection (version 2.4.0) requires ~> 0.4 or ~> 1.0
  ecto (version 3.7.1) requires ~> 0.4 or ~> 1.0
  ecto_sql (version 3.7.0) requires ~> 0.4.0 or ~> 1.0
  phoenix (version 1.6.0-rc.0) requires ~> 0.4 or ~> 1.0
  phoenix_live_view (version 0.16.3) requires ~> 0.4.2 or ~> 1.0
  plug (version 1.12.1) requires ~> 0.4.3 or ~> 1.0
  swoosh (version 1.5.0) requires ~> 0.4.2 or ~> 1.0
  telemetry_metrics (version 0.6.1) requires ~> 0.4 or ~> 1.0
  telemetry_poller (version 1.0.0) requires ~> 1.0
  tesla (version 1.3.3) requires ~> 0.4
  mix.lock specifies 1.0.0

** (Mix) Hex dependency resolution failed, change the version requirements of your dependencies or unlock them (by using mix deps.update or mix deps.unlock). If you are unable to resolve the conflicts you can try overriding with {:dependency, "~> 1.0", override: true}

So I try overriding:

defp deps do
  # ...
  {:telemetry_metrics, "~> 0.6", override: true},
  {:telemetry_poller, "~> 1.0", override: true},
  # ..
end

(…because {:telemetry} doesn’t exist)

This has no effect.

I’ve also tried $ rm -rf deps && mix deps.get to no avail.

$ mix -f deps mix.lock && mix deps.get causes an indefinite hand on Resolving hex dependencies...

I realize that release candidates are going to have problems but I’m just wondering if anyone has worked around this. I’m gun-shy about opening an issue to to 1.16 being in rc. Also, I can’t exclusively use LiveView tests as my app has a JS widget with drag and drop that LiveView tests don’t support.

Thanks!

Marked As Solved

mhanberg

mhanberg

Expert LSP Core Team

Hi, I think this is due to one of our dependencies using the Tesla library. That library was just bumped to relax the Tesla version constraint.

I’ll update Wallaby and cut a release.

Also Liked

mhanberg

mhanberg

Expert LSP Core Team

I released v0.29.0. Let me know if that works out for you.

Last Post!

tomthestorm

tomthestorm

Hi,
have the same problem , ver. 0.29.0 didn’t help.

Failed to use "mime" (version 2.0.2) because
  plug (version 1.12.1) requires ~> 1.0 or ~> 2.0
  swoosh (version 1.5.1) requires ~> 1.1 or ~> 2.0
  tesla (versions 1.3.0 to 1.4.3) requires ~> 1.0
  mix.lock specifies 2.0.2

Thanks in advance

Where Next?

Popular in Questions Top

rms.mrcs
Hi, I need to transform a list of numbers into a map where the keys are the indexes and the values are the original values of the list. ...
New
hariharasudhan94
I would like to know what is the best IDE for elixir development?
New
jononomo
For some reason my phoenix channels are working for me in my local dev environment, but as soon as I deploy via Docker, I get a 403 error...
New
openscript
Hello! Sorry for this astonishing simple question, but I’m really stuck. I try to set up the intellij-elixir plugin, but I don’t know ho...
New
nsuchy
Hi. I’ve noticed that Windows Powershell has it’s own IEX command and you cannot access Elixir’s IEX due to the conflict. This isn’t a cr...
New
shijith.k
I am trying to start a new phoenix project with elixir 1.9, but mix phx.new does not work. It says that ** (Mix) The task "phx.new" could...
New
pmjoe
I have a relationship of love and hate with Elixir. Lots of things are just absolutely right, but there are some things that are kind of ...
New

Other popular topics Top

JakeBecker
TL;DR: I’ve just released an implementation of Microsoft’s IDE-independent Language Server Protocol for Elixir. It adds language support ...
1144 54921 245
New
greenz1
I have a phoenix application from which a user can download multiple(5-6) files of size 1MB. I couldn’t find anything related to sending ...
New
gshaw
What is the idiomatic way of matching for not nil in Elixir? E.g., First way: defp halt_if_not_signed_in(conn, signed_in_account) when...
New
sorentwo
Hello! tl;dr Announcing Oban, an Ecto based job processing library with a focus on reliability and historical observability. After spen...
985 44532 311
New
WestKeys
Currently suffering from paralysis by [HTTP client] analysis. This is rather unusual in Elixirland as there tends to be consensus on the ...
New
Harrisonl
We have an ECS cluster with 4 services, where each task joins a single cluster, via discovery ECS discovery service. Currently when I de...
New

We're in Beta

About us Mission Statement