![]() I think tag = nil or undef should just error out as you state, its just not a valid case. So we could ponder a new semantic case for tag = nil if we wanted to so that it is actually meaningful, but it seems useless in the end. So being that this is nonsensical, I'd rather like you state return a warning/error. Even an empty tags array won't return anything here. I can, simply allow the nil to pass through in code (without the downcase) however PDB will throw an error, even if I fix this - you get nothing back, because a tag = nil call, is like asking if the tags array has any nil in it, which is impossible. So even if I raise an exception when the value is nil (which is easy to do), it will just be an error with no clue as to where in the manifest it occurred. Right now its just too far down into the system for us to do this, I believe for this to work it would require a change in Puppet, at least at first glance. The puppetdb termini as far as that code level cannot illicit exceptions that actually contain line numbers or locations in code that caused the problem. Okay, so doing some testing on this, and some small hacks on the code to see what is possible I've got a couple of points to make: Re: Puppet::Parser::Compiler failed with error NoMethodError: undefined method `downcase' for :undef:Symbol
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |