JILL24

FunctionClauseError on running mix rustler.new (no function clause matching in OptionParser.validate_swit)

when i tried to run mix rustler.new

** (FunctionClauseError) no function clause matching in OptionParser.validate_switch/1

The following arguments were given to OptionParser.validate_switch/1:

    # 1
    :module

Attempted function clauses (showing 1 out of 1):

    defp validate_switch({_name, type_or_type_and_modifiers})

(elixir 1.13.4) lib/option_parser.ex:623: OptionParser.validate_switch/1
(elixir 1.13.4) lib/enum.ex:1593: Enum."-map/2-lists^map/1-0-"/2
(elixir 1.13.4) lib/option_parser.ex:599: OptionParser.build_config/1
(elixir 1.13.4) lib/option_parser.ex:231: OptionParser.parse/2
(rustler 0.22.2) lib/mix/tasks/rustler.new.ex:36: Mix.Tasks.Rustler.New.run/1
(mix 1.13.4) lib/mix/task.ex:397: anonymous fn/3 in Mix.Task.run_task/3
(mix 1.13.4) lib/mix/cli.ex:84: Mix.CLI.run_task/2

8 comments

#rustler

3 822 8

2022-07-07 01:46:15 UTC

Most Liked

al2o3cr

@JILL24 This is a bug that was fixed in Rustler 0.23:

github.com/rusterlium/rustler

mix rustler.new broken on Elixir 1.13.0

opened 03:36PM - 05 Dec 21 UTC

closed 12:12AM - 07 Dec 21 UTC

dantswain

bug

Hi! When running `mix rustler.new` on Elixir 1.13, I get the following error: … ``` ** (FunctionClauseError) no function clause matching in OptionParser.validate_switch/1 The following arguments were given to OptionParser.validate_switch/1: # 1 :module Attempted function clauses (showing 1 out of 1): defp validate_switch({_name, type_or_type_and_modifiers}) (elixir 1.13.0) lib/option_parser.ex:623: OptionParser.validate_switch/1 (elixir 1.13.0) lib/enum.ex:1593: Enum."-map/2-lists^map/1-0-"/2 (elixir 1.13.0) lib/option_parser.ex:599: OptionParser.build_config/1 (elixir 1.13.0) lib/option_parser.ex:231: OptionParser.parse/2 (rustler 0.22.2) lib/mix/tasks/rustler.new.ex:36: Mix.Tasks.Rustler.New.run/1 (mix 1.13.0) lib/mix/task.ex:397: anonymous fn/3 in Mix.Task.run_task/3 (mix 1.13.0) lib/mix/cli.ex:84: Mix.CLI.run_task/2 (elixir 1.13.0) lib/code.ex:1183: Code.require_file/2 ``` I suspect this is a result of https://github.com/elixir-lang/elixir/pull/11019 - it looks like switch types will no longer default to string. This could arguably be called a bug in OptionParser but I couldn't find anywhere in the docs where it claims to allow switches specified without a type, so unless I missed that it's not like they broke any advertised behavior. I think you'd just need to update this line: https://github.com/rusterlium/rustler/blob/master/rustler_mix/lib/mix/tasks/rustler.new.ex#L33 to ``` @switches [module: :string, name: :string, otp_app: :string] ```

Post #2

msimonborg

You are on an older version of Rustler (0.22.2) where the mix rustler.new task appears incompatible with Elixir 1.13. See the changelog, specifically a fix in 0.23.0

Assuming you’re on Elixir 1.13, if you upgrade Rustler in your mix.exs {:rustler, "~> 0.25.0"} and run mix deps.update --all, then it should work

Post #6

al2o3cr

Hi @JILL24 - welcome to the Elixir forum!

We (the moderators) combined your posts into a single new thread as duplicate posting is against the forum rules.

In addition, consider opening a new thread when asking a mostly-unrelated question. The “mark as answered” feature doesn’t work if you add a new question to a months-old answered one.

Post #10