-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Closed
Description
Precheck
Checked and this looks like a bug.
Environment
Elixir & Erlang/OTP versions (elixir --version):
Erlang/OTP 23 [erts-11.2.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe]
Elixir 1.10.4 (compiled with Erlang/OTP 23)
and
Erlang/OTP 23 [erts-11.2.2] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe]
Elixir 1.11.4 (compiled with Erlang/OTP 23)
Operating system
Linux
Current behavior
Passing the --force flag to mix ecto.load causes it to run the compile task. It wrongly passes that flag to the dependency task.
Reproduction
git clone https://github.com/socialpaymentsbv/mix-flag-bug-example && cd mix-flag-bug-examplemix do deps.get, compilemix ecto.load --force- observe recompilation
Control run
Control run to make sure that the --force flag is indeed causing this and not something else.
mix ecto.load- Observe no recompilation
Expected behavior
Running mix ecto.load --force should not force recompilation. It should only "not ask for confirmation when loading data" as mix help ecto.load says.
In other (more generic) words: Mix – as it is with Erlang/OTP 22 – should not pass the flags supplied (e.g. --force) to the runned task (e.g. ecto.load) to dependant tasks (e.g. compile).
Workaround
In ecto.load the workaround that can be applied is passing the flag --no-compile.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels