On Tue, May 5, 2020 at 1:01 PM Zachary Kent <zachary.k...@puppet.com> wrote: > Thank you for such a thorough explanation of the issue you were seeing. We're > fixing this now and will put out a new version of PuppetDB with a fix ASAP > (likely in the next couple days).
Glad I could help! > The two options you mentioned as possible workarounds would both get the > job done and seem low risk, but it may be worth waiting for the version we're > planning on releasing soon if you're able. Knowing there's a solution in the pipeline, I can wait a little bit for it. We're not deploying a lot of new machines at the moment :D -- Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci Princeton University | ICBM Address: 40.346344 -74.652242 345 Lewis Library |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (267) 793-0852 | headlong into mystery." -Rush, 'Cygnus X-1' -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANnpg5T3a0tZiS8Yv0znWKg%2Bj_cmoEni0vV9FcxXj0arzMRZUw%40mail.gmail.com.