-
Notifications
You must be signed in to change notification settings - Fork 2
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
/data/common.yaml - file does not contain a valid yaml hash #6
Comments
|
Thanks for catching this. Can you test out the latest commit to see if that fixes things? If it does I'll tag a new release and publish it to the forge. |
|
It does indeed, thank you very much.
…On Mon, 24 Jan 2022 at 07:13, Phil Fenstermacher ***@***.***> wrote:
Thanks for catching this. Can you test out the latest commit to see if
that fixes things? If it does I'll tag a new release and publish it to the
forge.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABITFJJFSQYIBRR7VROU5BDUXTNX7ANCNFSM5MMBHJJA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I suspect time got away from you, can this fix be put on the forge? |
|
Thanks for the reminder. I just pushed this in 0.3.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Puppet complains that common.yaml does not contain a valid yaml hash. Should it change from
---to
--- {}?
The text was updated successfully, but these errors were encountered: