Jira (PDB-5593) Generating report data
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5593 Generating report data Change By: Rob Browning Fix Version/s: PDB 8.0.1 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.8946.1686610560030%40Atlassian.JIRA.
Jira (PUP-10639) Refresh cached Puppet CA on Puppet client
Title: Message Title Parker Leach updated an issue Puppet / PUP-10639 Refresh cached Puppet CA on Puppet client Change By: Parker Leach Labels: docs_reviewed Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.369858.1597923633000.8904.1686609120064%40Atlassian.JIRA.
Jira (PUP-10928) Add a setting to prevent falling back to non-rich data
Title: Message Title Parker Leach updated an issue Puppet / PUP-10928 Add a setting to prevent falling back to non-rich data Change By: Parker Leach Labels: docs_reviewed Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.388074.1613713885000.8893.1686607980050%40Atlassian.JIRA.
Jira (PUP-11723) Remove dependency on private class Concurrent::RubyThreadLocalVar
Title: Message Title Parker Leach updated an issue Puppet / PUP-11723 Remove dependency on private class Concurrent::RubyThreadLocalVar Change By: Parker Leach Labels: docs_reviewed Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.479493.1674511008000.8890.1686607320040%40Atlassian.JIRA.
Jira (FACT-3193) Delete facter-ng code/tests
Title: Message Title Josh Cooper updated an issue Facter / FACT-3193 Delete facter-ng code/tests Change By: Josh Cooper Fix Version/s: FACT 4.4.2 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.483283.1679449136000.8852.1686598800037%40Atlassian.JIRA.
Jira (FACT-3193) Delete facter-ng code/tests
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-3193 Delete facter-ng code/tests Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.483283.1679449136000.8853.1686598800086%40Atlassian.JIRA.
Jira (FACT-3193) Delete facter-ng code/tests
Title: Message Title Josh Cooper updated an issue Facter / FACT-3193 Delete facter-ng code/tests Change By: Josh Cooper Sprint: Phoenix 2023-06-21 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.483283.1679449136000.8851.1686598740101%40Atlassian.JIRA.
Jira (FACT-3193) Delete facter-ng code/tests
Title: Message Title Josh Cooper updated an issue Facter / FACT-3193 Delete facter-ng code/tests Change By: Josh Cooper Epic Link: PUP PA - 11660 5411 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.483283.1679449136000.8850.1686598740038%40Atlassian.JIRA.
Jira (FACT-1902) Confirm Facter 4 validates that external/custom/executable facts output proper UTF-8
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-1902
Confirm Facter 4 validates that external/custom/executable facts output proper UTF-8
Change By:
Josh Cooper
Modern versions of Puppet require that the data they serialize to JSON is proper UTF-8. Since facter collects data from different external sources, it's possible for facter data to be incorrectly encoded. Examples include: * String contains a valid UTF-16LE byte sequence, but the string's "encoding" method returns UTF-8 (Windows Registry) * String contains binary data, but "encoding" returns UTF-8 (EC2 userdata) * String contains the start of a valid multibyte UTF-8 sequnce, e.g. ("\xc3\x28") * String contains embedded nulls. Strictly speaking the "\u" code point is valid and is encoded as a single null byte, but it is surprising and can't be stored in Postgres. * String was generated by a child process based on the active code page (Windows CP1252), but the output is interpreted as UTF-8Facter's normalization should ensure: * All fact data contains valid UTF-8 data * If the string data is not valid, the invalid byte sequence an error should be replaced with logged stating the unicode replacement character, so custom or external fact that it is valid caused the issue. The fact should be omitted from the fact collection sent to the server and the agent run should continue * Same for embedded null values (different ticket) * A warning should be generated specifying the fact key -or value- with invalid data
Add Comment
This mess
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Gareth McGrillan commented on PDB-5633 Re: Investigate why (some?) command discards aren't including the stack No worries - any pointers to poke would be gratefully received! Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.484959.1682619597000.8787.1686587640024%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Joshua Partlow commented on PDB-5633 Re: Investigate why (some?) command discards aren't including the stack Sorry, Gareth, there must be something going on with Jira. I didn't get notified about any of these comments until today for some reason. Yes, your syntax is correct now, but I'm not sure about the best way to force a discard. Rob Browning? Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.484959.1682619597000.8752.1686585840031%40Atlassian.JIRA.
Jira (PDB-5647) Slow fact queries after PuppetDB 7 upgrade (comparing with PuppetDB 5) with GCP CloudSQL PostgreSQL
Title: Message Title Krzysztof Krzyżaniak commented on PDB-5647 Re: Slow fact queries after PuppetDB 7 upgrade (comparing with PuppetDB 5) with GCP CloudSQL PostgreSQL It looks like it's entirely connected with the PostgreSQL version, all versions higher than 9 have problems with that query. These are times we gathered for various combination of PuppetDB and PostgreSQL (in any case JIT is switched off): puppetdb5 & PostgreSQL13 real 0m24.315s user 0m0.006s puppetdb5 & PostgreSQL9.6 real 0m7.194s user 0m0.004s puppetdb 7.12.0 & PostgreSQL9.6 real 0m5.689s user 0m0.005s puppetdb 7.13.0 & PostgreSQL13 - combination not possible, doesn't work. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486416.168570735.6880.1686575700044%40Atlassian.JIRA.
