Jira (FACT-2609) Lspci resolver
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2609 Lspci resolver Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357839.1588775929000.69285.1590409800048%40Atlassian.JIRA.
Jira (FACT-2608) Xen resolver
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2608 Xen resolver Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357838.1588775882000.69284.1590408120291%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Thomas Goirand commented on PUP-10247 Re: Support ruby 2.7 Josh Cooper the idea that Puppet users should always be using puppetlabs packages and vendored Ruby interpreter is really a bad one. It's not acceptable from any point of view. Vendoring library is already a very bad practice, vendoring a language interpreter even more. Please stop saying this is a solution, when this is in fact a problem, and please make puppet work on Ruby 2.7 ASAP. When that is done, then Debian folks can work on packaging Puppet 6 in Debian, which is currently not possible because of Ruby 2.7 that lives there (and as a consequence in Ubuntu as well). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342962.1579675679000.69272.1590402240029%40Atlassian.JIRA.
Jira (PUP-10493) Puppet should ignore system ruby settings
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-10493 Puppet should ignore system ruby settings Change By: Ciprian Badescu Assignee: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357794.158876606.69269.1590398100160%40Atlassian.JIRA.
Jira (PUP-10505) Investigate and replace the running? method from Puppet
Title: Message Title
Ciprian Badescu commented on PUP-10505
Re: Investigate and replace the running? method from Puppet
cbadescu@ciprian:~/puppetlabs/puppet-PUP-10505$ grep -r 'running?' *
ext/windows/service/daemon.rb:while service.running? do
lib/puppet/provider/service/openbsd.rb: def running?
lib/puppet/provider/service/openbsd.rb:rcctl(:restart, @resource[:name]) if running?
lib/puppet/agent/locker.rb: def running?
lib/puppet/agent/locker.rb:#TRANSLATORS 'Puppet::Agent::Locker.running?' is a method name and should not be translated
lib/puppet/agent/locker.rb:message = _('Puppet::Agent::Locker.running? is deprecated as it is inherently unsafe.')
locales/puppet.pot:#. TRANSLATORS 'Puppet::Agent::Locker.running?' is a method name and should not be translated
locales/puppet.pot:msgid "Puppet::Agent::Locker.running? is deprecated as it is inherently unsafe."
spec/unit/provider/service/openbsd_spec.rb: context "#running?" do
spec/unit/provider/service/openbsd_spec.rb: expect(provider.running?).to be_truthy
Jira (PUP-10505) Investigate and replace the running? method from Puppet
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-10505 Investigate and replace the running? method from Puppet Change By: Ciprian Badescu Assignee: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358594.1589359223000.69263.1590395760027%40Atlassian.JIRA.
Jira (FACT-2634) Add acceptance test for error in custom facts
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2634
Add acceptance test for error in custom facts
Change By:
Bogdan Irimie
The test should contain two files with custom facts. The first file should contain 3 custom facts, with an error after the first fact e.g. {code} Facter.add(:custom_fact_1) do setcode do 'custom_fact_1_value' endend# some errornill.sizeFacter.add(:custom_fact_2) do setcode do 'custom_fact_2_value' endendFacter.add(:custom_fact_3) do setcode do 'custom_fact_3_value' endend{code} The second file should contain a custom fact e.g.{code}Facter.add(:custom_fact_4) do setcode do 'custom_fact_4_value' endend{code}We should check the fallowing: # Facter.to_hash works # Facter.value() returns correct value # Facter.value('custom_fact_1') returns 'custom_fact_1_value' # Facter.value('custom_fact_4') returns 'custom_fact_4_value' # Facter.value('custom_fact_2') does not return any value # Facter.value('custom_fact_3') does not return any value # Facter logs an error message when loading first file with custom facts
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2634) Add acceptance test for error in custom facts
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2634
Add acceptance test for error in custom facts
Change By:
Bogdan Irimie
The test should contain two files with custom facts. The first file should contain 3 custom facts, with an error after the first fact e.g.{code}Facter.add(:custom_fact_1) do setcode do 'custom_fact_1_value' endend# some errornill.sizeFacter.add(:custom_fact_2) do setcode do 'custom_fact_2_value' endendFacter.add(:custom_fact_3) do setcode do 'custom_fact_3_value' endend{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359856.1590391856000.69259.1590393420030%40Atlassian.JIRA.
Jira (FACT-2634) Add acceptance test for error in custom facts
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2634 Add acceptance test for error in custom facts Issue Type: Task Assignee: Unassigned Created: 2020/05/25 12:30 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359856.1
