Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no function clause matching cuttlefish_vmargs:'-stringify/1-lc$^0/1-0-'(undefined) [JIRA: RIAK-2498] #152

Open
rlipscombe opened this issue May 13, 2014 · 4 comments

Comments

@rlipscombe
Copy link

escript: exception error: no function clause matching 
                 cuttlefish_vmargs:'-stringify/1-lc$^0/1-0-'(undefined) (src/cuttlefish_vmargs.erl, line 13)
  in function  cuttlefish_escript:engage_cuttlefish/1 (src/cuttlefish_escript.erl, line 390)
  in call from cuttlefish_escript:generate/1 (src/cuttlefish_escript.erl, line 259)
@rlipscombe
Copy link
Author

It appears that you're required to have at least one setting with a vm_args mapping, and you have to have it in both the schema and in the source config file. This could do with either a better error message or a mention in the documentation (or both).

(I'm building this up from scratch because we're using relx for our releases).

@RJ
Copy link

RJ commented Apr 13, 2016

I ran into this too, i'm including a vmargs setting in my main schema too for now as a workaround.

Fix in cuttlefish_vmargs is probably just a clause to turn undefined into an empty list. I don't think any vmargs settings are strictly necessary.

stringify(undefined) -> [];
stringify(.....

@Basho-JIRA Basho-JIRA changed the title no function clause matching cuttlefish_vmargs:'-stringify/1-lc$^0/1-0-'(undefined) no function clause matching cuttlefish_vmargs:'-stringify/1-lc$^0/1-0-'(undefined) [JIRA: RIAK-2498] Apr 13, 2016
@rlipscombe
Copy link
Author

Having just found this again after more than 5 years, I'm going to expand on my comment. You need at least schema/vm_args.schema containing:

{mapping, "nodename", "vm_args.-sname", []}.

...and you need a nodename = foo setting in app.conf.

@rlipscombe
Copy link
Author

...but #152 (comment) works fine, once you persuade rebar3 to actually rebuild the damn thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants