Jira (BOLT-905) [SPIKE] Investigate performance issues around concurrent connections over winrm
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-905 [SPIKE] Investigate performance issues around concurrent connections over winrm Change By: Michael Smith Affects Version/s: PE 2019.0 Affects Version/s: PE 2019.0.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-978) Package Bolt for Fedora 27/28
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-978 Package Bolt for Fedora 27/28 Issue Type: Improvement Assignee: Unassigned Created: 2018/11/14 3:31 PM Labels: docs Priority: Normal Reporter: Michael Smith Steps are: ci-job-configs update to build bolt-runtime on fedora 27/28, produce build, copy those configs to bolt-vanagon, update ci-job-configs to build puppet-bolt on fedora 27/28. Add install docs. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-978) Package Bolt for Fedora 27/28
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-978 Package Bolt for Fedora 27/28 Change By: Michael Smith Steps are: ci-job-configs update to build bolt-runtime on fedora 27/28, produce build, copy those configs to bolt-vanagon, update ci-job-configs to build puppet-bolt on fedora 27/28. Add install docs. Requested at https://github.com/puppetlabs/bolt/issues/750. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-977) Send release announcements (Bolt 1.3.0)
Title: Message Title Melissa Amos commented on BOLT-977 Re: Send release announcements (Bolt 1.3.0) This didn't go well. Discovered a bug in Chrome that prevents sending mail from the alternate mail address puppet-product-upda...@puppet.com. Message just fails to send. I did manage to get one email sent (to internal-puppet-product-upda...@puppet.com) when I used an incognito tab, however the message doesn't appear in my Sent items, but it does appear in Kate Lopresti's sent items. She's also set up with puppet-product-upda...@puppet.com as an alternate email; still, this makes no sense. When I sent a second email, also from an incognito tab, to the remaining three email addresses described in this ticket, they all bounced back. I tried again, with just one addressee, and it also bounced. I don't have time to troubleshoot this further today, because I have to go pick up a kiddo. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Henrik Lindberg commented on PUP-9294 Re: Raise Error when a legacy function illegally defines methods Added a link to predocs - which also describes how to refactor a 3x function to 4x. https://docs.google.com/document/d/1_KToXDDjbe0HQ6I4UqckNqcJ-AHreH_dmd_A1Cr85jU/edit#heading=h.7tr91p8l7qjp Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9294 Raise Error when a legacy function illegally defines methods Change By: Henrik Lindberg Component/s: Language Component/s: Functions Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title Jean Bond commented on PUP-9311 Re: User resource doesn't remove user from windows group Josh Cooper, I've changed this in the 5.5 and 6.0 docs, and PR'd to the puppet repo with a change to lib/puppet/type/user.rb (https://github.com/puppetlabs/puppet/pull/7234) . Let me know if you need me to change the PR at all; I'm a bit rusty on PRing to the code repo. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Josh Cooper commented on PUP-9313 Re: String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows We worked around the issue in puppet in https://github.com/puppetlabs/puppet/commit/b3da360183de1bab4d12b5a54fb56ee99c1bf79a Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Josh Cooper commented on PUP-9313 Re: String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Also https://github.com/yaml/libyaml/issues/60 and this PR https://github.com/yaml/libyaml/pull/122, specially this commit https://github.com/yaml/libyaml/commit/56f4b17221868593d6903ee58d6d679b690cf4df Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title
Josh Cooper commented on PUP-9313
Re: String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Lars replied:
I guess it's due to the update of libyaml from version 0.1.7 to 0.2.1 between these two releases. You can query the library version by YAML::LIBYAML_VERSION . Ubuntu-18.10 is still at version 0.1.7, so that this issue doesn't show up there. Maybe the same is true on MacOS.{quote} I verified there is a libyaml difference on windows:
C:\>c:\rubyinstaller-2.4.5-1-x64\bin\ruby.exe yaml.rb
Ruby 2.4.5p335
Psych 2.2.2
YAML 0.2.1
--- string
C:\>c:\rubyinstaller-2.4.4-2-x64\bin\ruby.exe yaml.rb
Ruby 2.4.4p296
Psych 2.2.2
YAML 0.1.7
--- string
...
This might be related https://github.com/yaml/libyaml/issues/123?
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title Josh Cooper commented on PUP-9311 Re: User resource doesn't remove user from windows group Jean Bond I'm thinking we should update https://puppet.com/docs/puppet/5.0/resources_user_group_windows.html#group-membership to read: If you want to ensure a user belongs to only the groups listed in the manifest, and no more, you can specify the membership attribute for the user. Also in the user type reference generated from puppet code (lib/puppet/type/user.rb), we should mention that auth_membership is specific to managing Solaris authorizations (via the auths CLI). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title Josh Cooper assigned an issue to Jean Bond Puppet / PUP-9311 User resource doesn't remove user from windows group Change By: Josh Cooper Assignee: Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9311 User resource doesn't remove user from windows group Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title
Josh Cooper commented on PUP-9311
Re: User resource doesn't remove user from windows group
Alex Davies You'll want to use the membership user parameter, not auth_membership, e.g
user { '...':
ensure => present,
...
membership => 'inclusive',
The auth_membership user parameter is specific to the auths property on Solaris. It's confusing because the group type has an auth_membership parameter that does control whether members is the partial vs complete list. The docs look like they need updating, so we can repurpose this ticket for that.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-956) Add wait_until_available function to Bolt
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-956 Add wait_until_available function to Bolt Change By: Melissa Amos Labels: docs docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Henrik Lindberg commented on PUP-9294 Re: Raise Error when a legacy function illegally defines methods Using the Ripper class works fine - will update the PR to use that to walk the parsed code instead of trying to protect the classes from getting added methods. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-962) docker transport
Title: Message Title Melissa Amos commented on BOLT-962 Re: docker transport Fixed. Thanks for the review. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-795) Bolt needs a `config print` action
Title: Message Title Charlie Sharpsteen commented on BOLT-795 Re: Bolt needs a `config print` action Having a quick way to determine the effective modulepath is even more important now that Bolt can compile and apply puppet manifests. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Henrik Lindberg commented on PUP-9294 Re: Raise Error when a legacy function illegally defines methods This turned out to be incredibly difficult in practice. There are 4 different things to protect against - 2 per way the functions are loaded A 3x function loaded by the autoloader - which happens in lots of tests and when explicitly calling scope.function_xxx A 3x function loaded by the 4x loader - which happens when language loads/evaluates calls The two things to protect against are: a def method inside of the 3x function body a def method outside of the 3x function body That means there are 4 different classes/modules that will have a method added. By defining callbacks that catch when a method is added in those four places it was possible to raise errors. However - since adding instance methods is also something that takes place when testing / mocking, the same guards are triggered by legitimate testing. Two of the locations are hit when loading the function, so there it is possible to have a flag that indicates that loading is taking place, but for the methods defined inside of the code body, that does not take place until the function is called! That means it is impossible to catch those at load time unless the ruby code being loaded is parsed and walked and that has the cost of parsing the ruby code twice (once with Ripper, and once for real). Att runtime, trying to protect the classes/methods is very kludgy as the triggering of the "method added" callbacks reacts to adding those very callbacks. An alternative is to write a custom Rubocop rule to catch the illegal 3x functions. Armed with that, users can test their modules and the forge can use that to downflag modules with illegal functions. This solution does not burden the runtime - the illegal functions would simply not work but there will not be any special error messages. At this time, I am exploring the option of using the Ripper (internal Ruby parser) to find illegal defines as the Ripper works in MRI since 1.9 as well as in jRuby. Add Comment
Jira (BOLT-959) Plan with no return value is never marked complete in PE
Title: Message Title Melissa Amos commented on BOLT-959 Re: Plan with no return value is never marked complete in PE Here's the release note: https://docs-preview.webteam.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#plans-with-no-return-value-weren-t-marked-complete-in-pe-1-3-0 (Preview credentials here: https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=COM=Puppet.com+access) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-971) Some functions not available in BoltSpec run_plan
Title: Message Title Melissa Amos commented on BOLT-971 Re: Some functions not available in BoltSpec run_plan Here's the release note: https://docs-preview.webteam.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#some-functions-weren-t-available-in-the-boltspec-plans-library-1-3-0 (Preview credentials here: https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=COM=Puppet.com+access) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-962) docker transport
Title: Message Title Melissa Amos commented on BOLT-962 Re: docker transport Here are doc updates: https://docs-preview.webteam.puppet.com/docs/bolt/dev/bolt_configuration_options.html#docker-transport-configuration-options https://docs-preview.webteam.puppet.com/docs/bolt/dev/bolt_options.html#concept-8521 https://docs-preview.webteam.puppet.com/docs/bolt/dev/bolt_new_features.html#docker-transport-for-running-commands-on-containers-1-3-0 (Preview credentials here: https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=COM=Puppet.com+access) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
