There are multiple (transitive) dependencies to chatterbox, which appears to have warnings as errors set, while using a deprecated erlang API
Erlang/OTP 21 [erts-10.0] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1]
Elixir 1.6.6 (compiled with OTP 19)
Linux *redacted* 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
And building as recommended in the README.md
ghard@*redacted*:~/src/MongoosePush$ MIX_ENV=prod mix do deps.get, certs.dev, docker.build, docker.release
*** stuff deleted ***
==> Compiling src/h2_connection.erl failed
src/h2_connection.erl:351: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead
==> mongoose_push
** (Mix) Could not compile dependency :chatterbox, "/home/ghard/.mix/rebar3 bare compile --paths "/home/ghard/src/MongoosePush/_build/prod/lib/*/ebin"" command failed. You can recompile this dependency with "mix deps.compile chatterbox", update it with "mix deps.update chatterbox" or clean it with "mix deps.clean chatterbox"
Changing the compile opts for chatterbox will cause it to fail building the next module with a transitive chatterbox dependency. I am not adept enough in mix/elixir to figure out how to pass an exception to the build that would compile all modules matching X with warnings as errors disabled.
Is there an elegant workaround / fix or need I spoof whatever URL chatterbox gets loaded from from locally?
There are multiple (transitive) dependencies to chatterbox, which appears to have warnings as errors set, while using a deprecated erlang API
And building as recommended in the README.md
Changing the compile opts for chatterbox will cause it to fail building the next module with a transitive chatterbox dependency. I am not adept enough in mix/elixir to figure out how to pass an exception to the build that would compile all modules matching X with warnings as errors disabled.
Is there an elegant workaround / fix or need I spoof whatever URL chatterbox gets loaded from from locally?