Bug #893

Use of metaparameters causes poor error message

Added by Matt Palmer over 4 years ago. Updated over 4 years ago.

Status:Closed Start date:
Priority:Normal Due date:
Assignee:Luke Kanies % Done:

0%

Category:language
Target version:0.24.0
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

site.pp:

define x($loglevel) {
}

Produces this error message in the Puppetmaster:

err: Could not parse; using old configuration:  is a metaparameter; please choose another name at site.pp:2
err: undefined method @findclass' for nil:NilClass

Note the lack of information as to what, precisely, is the metaparameter, and the fact that the error is indicated as being on line 2 instead of line 1. By the time you have a half-dozen parameters and a 100 line define, the error message becomes completely unhelpful.

The name of the metaparameter whose turf I’ve infringed on needs to be given, at the very least; fixing the line number would be very helpful too, but I know what racc is like…

History

Updated by Luke Kanies over 4 years ago

  • Status changed from 1 to 2

Updated by Luke Kanies over 4 years ago

  • Status changed from 2 to Closed
  • 7 set to fixed

Fixed in commit:6b2c0d8016e39589f6dd9fa50605fb03e31965a3:

Could not parse for environment development: require is a metaparameter; please choose another parameter name in the yay definition at /Users/luke/bin/test.pp:5

The line number will have to wait for a different bug.

Also available in: Atom PDF