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

fix future parser error #504

Merged
merged 1 commit into from
Oct 2, 2014
Merged

Conversation

steeef
Copy link

@steeef steeef commented Sep 16, 2014

I was receiving this error when using future parser on Puppet 3.7.1:

This Type-Name is not productive. A non productive construct may only be placed last in a block/sequence at /srv/puppet-environments/staging/modules/postgresql/manifests/server/database.pp:73:3

This should fix it.

@edestecd
Copy link

Awesome, I've been fighting this one... Thanks for the fix.

@Timokasse
Copy link

Please merge ASAP.
Thanks.

@greg0ire
Copy link

👍 please merge

@setola
Copy link

setola commented Sep 29, 2014

👍 I join the choir: please merge!

@igalic
Copy link
Contributor

igalic commented Sep 30, 2014

see also #505 ; ping @mhaskel

@greg0ire
Copy link

greg0ire commented Oct 2, 2014

ping @hunner : The bug is a deal-breaker, and the fix is a no-brainer change : 1 character is wreaking havoc! Can you please merge this ?

cmurphy added a commit that referenced this pull request Oct 2, 2014
@cmurphy cmurphy merged commit ad75c3e into puppetlabs:master Oct 2, 2014
@cmurphy cmurphy mentioned this pull request Oct 2, 2014
@greg0ire
Copy link

greg0ire commented Oct 2, 2014

Thank you @cmurphy !

@Ramesh7 Ramesh7 added the bugfix label Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants