Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Jorie Tappa commented on PUP-6258 Re: Update Puppet OID lists to add new authorized extensions Moses Mendoza That docs page belongs to Nicholas Fagerlund (at least according to our content inventory) and it looks like it hasn't been updated in forever (if ever since creation?) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Moses Mendoza commented on PUP-6258 Re: Update Puppet OID lists to add new authorized extensions Was looking at the docs for this at https://docs.puppet.com/puppet/4.10/ssl_attributes_extensions.html#recommended-oids-for-extensions and discovered this new arc is completely undocumented. It looks like it shipped in 4.6 and Puppet is on 4.10... Can we get that fixed? cc Garrett Guillotte Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3477) (maint) Update EZBake plugin to 0.1.9
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3477 (maint) Update EZBake plugin to 0.1.9 Issue Type: Bug Assignee: Unassigned Created: 2017/04/24 2:51 PM Priority: Normal Reporter: gepetto-bot This will cause a snapshot artifact to be deployed on promotion to PE. The full version of that artifact will be listed in the EZBake manifest & project_data.yaml files. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Eric Sorenson commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf Ryan Coleman it's in the description - you can use a command line argument. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5975) Remove Range#intersection monkey patch
Title: Message Title Thomas Hallgren commented on PUP-5975 Re: Remove Range#intersection monkey patch I'm confident, it will be, as soon as semantic_puppet 1.0 is released and we've updated the vendored version PUP-7431. Right now I'm not 100% sure. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5889) Add a --strict flag to Puppet
Title: Message Title Chris Denneen commented on PUP-5889 Re: Add a --strict flag to Puppet Henrik Lindberg Where would that be? require 'puppetlabs_spec_helper/module_spec_helper' Dir[File.absolute_path(File.dirname(__FILE__) + '/support/*.rb')].each do |f| require f end begin require 'spec_helper_local' rescue LoadError => e handle_error(e) end
Jira (FACT-1614) move and update verify fact tests into fact directory
Title: Message Title Eric Delaney created an issue Facter / FACT-1614 move and update verify fact tests into fact directory Issue Type: Task Assignee: Eric Delaney Created: 2017/04/24 11:27 AM Priority: Normal Reporter: Eric Delaney Move the tests verify_facts.rb, verify_mountpoints.rb, and operatingsystem_detection_after_clear_on_ubuntu.rb into the facts directory and update the tests for code style, TestRail ID's, and risk tags Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Josef David S. Prado commented on PUP-2782 Re: Yumrepo target attribute does not work Hi Guys, can anyone tell me is this works in any of the available puppet versions or if it a bug taht affects all of then? I´m facing it and I would like to decide if I will upgrade to a newer version or just stop trying to use yumrepo. Regards, Josef Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7463) Pin of net-ssh to ~> 2.1 is incompatible with Beaker's ~> 4.0
Title: Message Title
Ethan Brown commented on PUP-7463
Re: Pin of net-ssh to ~> 2.1 is incompatible with Beaker's ~> 4.0
Dominic Cleal I think you may have just so happened to try Puppet#master after a bad merge-up from stable to master (fixed in https://github.com/puppetlabs/puppet/commit/9ce6842876a5d97989f8538d10deae8d3389cd4e)
While the runtime dependency of ~> 2.1 did initially make it into .gemspec, we did notice the same problem with Beaker, and fixed it in https://github.com/puppetlabs/puppet/commit/c42a0b7e5f080d0696549e25fafee760a44f3f4d with:
s.add_runtime_dependency(%q, [">= 3.0", "< 5"]) if Gem::Version.new(RUBY_VERSION) >= Gem::Version.new('2.0.0')
Please close once you verify everything is good on your end.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-5975) Remove Range#intersection monkey patch
Title: Message Title Henrik Lindberg commented on PUP-5975 Re: Remove Range#intersection monkey patch Thomas Hallgren I lost track of where we are with respect to support for SemVer and the logic in PMT. Is it safe to use drop the monkey patch and and modify the test in semver_spec.rb ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5974) Remove IO#binwrite monkey patch
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5974 Remove IO#binwrite monkey patch Change By: Henrik Lindberg Release Notes Summary: Internal concern. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7402) handle trailing slashes in references between file resources
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7402 handle trailing slashes in references between file resources Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests; existing acceptance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7402) handle trailing slashes in references between file resources
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7402 handle trailing slashes in references between file resources Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (FACT-1611) Update external fact stderr tests
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Facter / FACT-1611 Update external fact stderr tests Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7457) Differing behavior between manual puppet run and daemon agent run
Title: Message Title Michael McCormac commented on PUP-7457 Re: Differing behavior between manual puppet run and daemon agent run Moses Mendoza Thanks for your reply! I've attached all relevant files as requested, let me know if you have any questions... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7457) Differing behavior between manual puppet run and daemon agent run
Title: Message Title Michael McCormac updated an issue Puppet / PUP-7457 Differing behavior between manual puppet run and daemon agent run Change By: Michael McCormac Attachment: puppet_daemon_debug.log Attachment: puppet_daemon.log Attachment: puppet_manual_debug.log Attachment: puppet_manual.log Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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
Jira (PUP-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Thomas Hallgren commented on PUP-6694 Re: The Puppet Data type should be limited to JSON types. Henrik Lindberg, if an unparameterized Hash or Array type doesn't default to being Data compliant, what do you suggest we use instead? One idea could be to use Puppet::LookupKey and Puppet::LookupValue. The key is then constrained to string or numeric and the value is basically everything but runtime. Introducing something that is in between that and Data doesn't sound very appealing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4605) With a systemd masked service: 'enable=true ensure=running' doesn't work
Title: Message Title Taras Kostyuk updated an issue Puppet / PUP-4605 With a systemd masked service: 'enable=true ensure=running' doesn't work Change By: Taras Kostyuk Affects Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4651) systemd service provider starts/enables in the wrong order
Title: Message Title
Taras Kostyuk commented on PUP-4651
Re: systemd service provider starts/enables in the wrong order
OS: CentOS 7.3 SELinux: enforcing Puppet version: 4.10.0
service { "any-service": enable => true, ensure => running, provider => systemd, }
As default selinux policy on Centos prevents enabling already started systemd service a service should be enabled before starting.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7463) Pin of net-ssh to ~> 2.1 is incompatible with Beaker's ~> 4.0
Title: Message Title Moses Mendoza commented on PUP-7463 Re: Pin of net-ssh to ~> 2.1 is incompatible with Beaker's ~> 4.0 ping Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4651) systemd service provider starts/enables in the wrong order
Title: Message Title Taras Kostyuk updated an issue Puppet / PUP-4651 systemd service provider starts/enables in the wrong order Change By: Taras Kostyuk Affects Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4605) With a systemd masked service: 'enable=true ensure=running' doesn't work
Title: Message Title Taras Kostyuk commented on PUP-4605 Re: With a systemd masked service: 'enable=true ensure=running' doesn't work The issue still exists with selinux running enforcing mode. OS: CentOS 7.3 SELinux: enforcing Puppet version: 4.10.0 As default selinux policy on Centos prevents enabling already started systemd service a service should be enabled before starting. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (FACT-1238) Facter should respect long-form hostnames to populate hostname, domain, and FQDN
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-1238 Facter should respect long-form hostnames to populate hostname, domain, and FQDN Change By: Kurt Wall Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Karen Van der Veer Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3464 Make a deterministic version of the sync convergence test Change By: Karen Van der Veer Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (FACT-1356) External facts should be able to return structured data
Title: Message Title
Paul W commented on FACT-1356
Re: External facts should be able to return structured data
Is there an example on how this is working with a external PowerShell script?
Tried to put a foo.ps1 file in my module's facts.d folder:
$var = "bar"
Write-Host "{ `"foo`":`"$var`" }"
Running Facter in debug mode I receive the following messages:
DEBUG leatherman.execution:92 - executing command: C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive -NoLogo -ExecutionPolicy Bypass -File C:/ProgramData/PuppetLabs/puppet/cache/facts.d\foo.ps1
DEBUG | - { "foo":"bar" }
DEBUG puppetlabs.facter - ignoring line in output: { "foo":"bar" }
DEBUG leatherman.execution:688 - process exited with exit code 0.
DEBUG puppetlabs.facter - completed resolving facts from powershell script "C:/ProgramData/PuppetLabs/puppet/cache/facts.d\foo.ps1".
Jira (FACT-1613) Update regression ticket tests
Title: Message Title Eric Delaney updated an issue Facter / FACT-1613 Update regression ticket tests Change By: Eric Delaney QA Risk Assessment Reason: Updating the automated tests QA Risk Assessment: Needs Assessment Automate QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Geoff Nichols Sprint: Agent N+ 2 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Agent N+ 2 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Sprint: Agent N+2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Thomas Hallgren commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Jesse Scott, I'm "thallgren" with email "thomas.hallg...@puppet.com" at rubygems.org. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title Thomas Hallgren commented on PUP-25 Re: Resource defaults aren't completely evaluated by the compiler A reproducer for the problem described in this ticket would be very helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7444) Regex match integer silently fails
Title: Message Title Tom De Vylder commented on PUP-7444 Re: Regex match integer silently fails Catalog Preview (or GH's Octocatalog) isn't something I've spent too much time looking into because . I usually rely heavily on rspec-puppet and/or Beaker mostly due to prior experience with both. They both have saved my hide countless times in the past for which I've very grateful. If I hadn't read about the regex change in the changelog I would have had a hard time figuring out why a particular test failed. Any new code I write does get data typed. I try to enforce this as much as possible, it's just not always feasible for old code. In the past I used stdlib validate_*() but that has been deprecated in recent versions. However I've just run into stdlib is_a today, so that should probably cover the edge cases where I can't data type the input for a variety of reasons beyond my control. Hadn't heard of puppet-debugger before. After a quick glance I hope to one day see a Puppet supported version of or alternative to this as part of the SDK. Definitely something to look into along with Catalog Preview! Changing the language isn't necessary nor is it expected. My sole request was to make some of the changes (more) visible to users. It's pretty clear now that in this case it's not as feasible as I'd have hoped it to be. Thank you for taking the time to explain it as clear as you have! I'll go ahead and close this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-569) Hiera filecache class should not store nil when an exception is thrown
Title: Message Title Thomas Hallgren commented on HI-569 Re: Hiera filecache class should not store nil when an exception is thrown A stack trace from the server log would be very helpful to isolate this problem. If there's a chance to try an upgrade to PE 2017.1.x/Puppet Agent 1.9.x, then that might solve the problem. Especially if the suspicion is that it stems from the Hiera Filecache class (it's no longer in use). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
