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

Error messages for missing fields which are arguments to functions are not clear. #1452

Closed
nathanielc opened this issue Jun 23, 2017 · 1 comment
Assignees

Comments

@nathanielc
Copy link
Contributor

If you call a function in a lambda expression and the field is missing as an argument to the function you get and error message about the function not having a function signature for missing values and no mention of which field is missing is given.

See https://community.influxdata.com/t/kapacitor-shiftnode-and-join-in-stream/1401/2 for an example.

@nathanielc nathanielc assigned nathanielc and desa and unassigned nathanielc Jun 23, 2017
@nathanielc nathanielc changed the title Error messages for missing fields are arguments to functions are not clear. Error messages for missing fields which are arguments to functions are not clear. Jun 23, 2017
@desa
Copy link
Contributor

desa commented Jul 6, 2017

I agree that the error is super unhelpful, but I'm not exactly sure what the error should be in the case of

|eval(lambda: max("x",float("y")))

when "x" is missing or has value of another invalid type.

Should I print out all of the arguments? Maybe something like

 E! Cannot call function "max" with args signature ("x": missing, float("y"): float), available signatures are [(float, float)].

Or I could get more fine grained and only list the parameters that are invalid. This approach would be more involved.

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

No branches or pull requests

2 participants