'No keyword argument' macro error does not report location of bad call

[markberger]

Describe the bug

If a macro is supplied a keyword arg that does not exist, the output message does not return the file and line number of the bad macro call.

Steps To Reproduce

Call an existing macro with a bad argument, for example:

  SELECT {{ dbt_utils.star(from=ref('my_model'), excepts=[]) }}
  FROM {{ ref('my_model') }}

excepts should be except. Then run dbt compile:

$ dbt compile
Running with dbt=0.15.1
Encountered an error:
Compilation Error in macro star (macros/sql/star.sql)
  macro 'dbt_macro__star' takes no keyword argument 'excepts'

Expected behavior

Also give file name and line number of the bad macro call

Screenshots and log output

System information

Which database are you using dbt with?

• postgres
• redshift
• bigquery
• snowflake
• other (specify: ____________)

The output of dbt --version:
0.15.1

The operating system you're using:
macOS mojave

The output of python --version:
3.6.5

Additional context

Add any other context about the problem here.

[drewbanin]

Thanks for the report @markberger! We'll check it out