Jira (PUP-10959) Lock loaders using a single central lock

2021-04-07 Thread Patrick Carlisle (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10959  
 
 
  Lock loaders using a single central lock   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)  
 
 

 
   
 

  
 

  
 

   





-- 
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.390496.1615338623000.3644.1617820380130%40Atlassian.JIRA.


Jira (PUP-10959) Lock loaders using a single central lock

2021-03-17 Thread Patrick Carlisle (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10959  
 
 
  Lock loaders using a single central lock   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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.390496.1615338623000.168350.1615998300085%40Atlassian.JIRA.


Jira (PUP-10483) LOAD_PATH can get corrupted when multithreading is on

2020-04-30 Thread Patrick Carlisle (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10483  
 
 
  LOAD_PATH can get corrupted when multithreading is on   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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.357470.1588282648000.52543.1588287660041%40Atlassian.JIRA.


Jira (PUP-10483) LOAD_PATH can get corrupted when multithreading is on

2020-04-30 Thread Patrick Carlisle (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10483  
 
 
  LOAD_PATH can get corrupted when multithreading is on   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/04/30 2:37 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-10318) Class definition errors in multhreaded when using environment caching

2020-03-05 Thread Patrick Carlisle (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10318  
 
 
  Class definition errors in multhreaded when using environment caching   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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.347802.158281950.5999.1583443080024%40Atlassian.JIRA.


Jira (FACT-2390) make facter 2x recursion check thread-safe

2020-02-19 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2390  
 
 
  make facter 2x recursion check thread-safe   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/02/19 4:14 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 This is not really needed for users but this version is still used in testing and it's easier for us to fix this for now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
  

Jira (FACT-2390) make facter 2x recursion check thread-safe

2020-02-19 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2390  
 
 
  make facter 2x recursion check thread-safe   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.347008.1582157687000.32965.1582157880336%40Atlassian.JIRA.


Jira (PUP-9932) [SPIKE] Can we make 3x functions loaders thread-safe?

2020-02-04 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9932  
 
 
  [SPIKE] Can we make 3x functions loaders thread-safe?   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306743.1556579117000.13113.1580837700903%40Atlassian.JIRA.


Jira (PUP-10231) check use of class variables for threaded compilation

2020-01-13 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10231  
 
 
  check use of class variables for threaded compilation   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341857.1578938336000.21159.1578938400142%40Atlassian.JIRA.


Jira (PUP-10231) check use of class variables for threaded compilation

2020-01-13 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10231  
 
 
  check use of class variables for threaded compilation   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/13 9:58 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 Make sure we aren't storing compilation state in a way that will cause problems when a different thread can have a different catalog compiling.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

Jira (PUP-10163) Evaluate remaning singleton classes for thread safety

2019-12-16 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10163  
 
 
  Evaluate remaning singleton classes for thread safety   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338277.1575658473000.578.1576518720211%40Atlassian.JIRA.


Jira (PUP-10024) Make environment caching thread safe

2019-09-18 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10024  
 
 
  Make environment caching thread safe   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Key: 
 SERVER PUP - 2617 10024  
 
 
Project: 
 Puppet  Server  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323043.1567196846000.104386.1568831940681%40Atlassian.JIRA.


Jira (PUP-9931) Make Context thread local

2019-08-19 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9931  
 
 
  Make Context thread local   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306716.1556578082000.62017.1566255960188%40Atlassian.JIRA.


Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold

2019-05-22 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-9564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet upgrades debian packages with pending updates when setting them on hold   
 

  
 
 
 
 

 
 This may be related to a systemwide apt problem that I'm working on, should have something tomorrow so feel free to leave it for now.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300439.1552654564000.18198.1558570860226%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold

2019-05-22 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-9564  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet upgrades debian packages with pending updates when setting them on hold   
 

  
 
 
 
 

 
 This is failing acceptance https://jenkins-platform.delivery.puppetlabs.net/job/platform_puppetserver_integration-system_no-conditional_full-5.3.x/224/  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300439.1552654564000.18001.1558565580203%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9185) Format Handler logs exceptions at too high a level

2018-10-17 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9185  
 
 
  Format Handler logs exceptions at too high a level   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes Summary: 
 In 6.0, Puppet logged an exception (with full stack trace) at the error level every time it needed to fall back to encoding a catalog in PSON. This can happen under normal circumstances and may cause the logs to fil up with errors when nothing is really wrong. This is now changed to log these at the debug level.  
 

  
 
 
 
 

 
 
 

 
 
 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-9185) Format Handler logs exceptions at too high a level

2018-10-17 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9185  
 
 
  Format Handler logs exceptions at too high a level   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-9212) add acceptance tests for vault lookup

2018-10-05 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9212  
 
 
  add acceptance tests for vault lookup   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/05 12:26 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 Add automated acceptance testing that runs puppet and vault to the vault_lookup module.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 
   

Jira (PUP-9185) Format Handler logs exceptions at too high a level

2018-10-05 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9185  
 
 
  Format Handler logs exceptions at too high a level   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Fix Version/s: 
 PUP 6.0.z  
 
 
Fix Version/s: 
 PUP 6.0.3  
 

  
 
 
 
 

 
 
 

 
 
 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-9185) Format Handler logs exceptions at too high a level

2018-09-27 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9185  
 
 
  Format Handler logs exceptions at too high a level   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.0.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/09/27 1:36 PM  
 
 
Fix Versions: 
 PUP 6.0.z  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 I made a [https://github.com/puppetlabs/puppet/commit/2dc6f510bf2313bbbc0013f08182918f3986355f|change] in Puppet 6 to log FormatError exceptions that were silently swallowed, but the interface to log at a debug level didn't work consistently so these are logged as errors even though they can be encountered in normal operation and may not be errors.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

Jira (PUP-8601) agent should support rich data content negotiation

2018-09-14 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8601  
 
 
  agent should support rich data content negotiation   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes Summary: 
 The `rich_data` setting is now enabled by default. Catalog requests have two new content-types, `application/vnd.puppet.rich+json` and `application/vnd.puppet.rich+msgpack`, that are used when both master and agent have this enabled (and depending on whether `preferred_serialization_format` is `json` or `msgpack`).  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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-9138) Puppet should save cached catalogs with rich_data when rich_data is enabled

2018-09-13 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9138  
 
 
  Puppet should save cached catalogs with rich_data when rich_data is enabled   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Summary: 
 Puppet should  render json  save cached catalogs  with  rich_data_json  rich_data  when rich_data is  used  enabled  
 

  
 
 
 
 

 
 
 

 
 
 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-8733) File type redefined when required in code

2018-09-04 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8733  
 
 
  File type redefined when required in code   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes Summary: 
 Fix an issue running in JRuby where we didn't store autoloaded paths in the same way that the JRuby implementation did, leading to a bug where a type or provider could get loaded more than once.  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-8591) Actually delete webrick

2018-09-04 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8591  
 
 
  Actually delete webrick   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes Summary: 
 Webrick support (previous deprecated) has been removed. This means that the `puppet master` command no longer exists. To run puppet as a server you must use puppetserver.  
 
 
Release Notes: 
 Deprecation  
 

  
 
 
 
 

 
 
 

 
 
 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-8601) agent should support rich data content negotiation

2018-08-27 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: agent should support rich data content negotiation   
 

  
 
 
 
 

 
 For now I've just threaded the rich_data setting through the context instead of settings and actually it is working, so I seem to have the basics going here with one mimetype that's negotiated.  
 

  
 
 
 
 

 
 
 

 
 
 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-8601) agent should support rich data content negotiation

2018-08-27 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: agent should support rich data content negotiation   
 

  
 
 
 
 

 
 How little of this can we do in the next two weeks without making life hard later? Can we define one mimetype that does the current default rich_data format and leave options to later? Maybe include them in the string but not allow changing them for now. I've started to look at threading this through from the request and it seems less trivial than I thought (checks global or environment level settings right now), but I'm not really familiar at all with how rich data encoding works in the actual puppet codebase. I think I'll need help with that side of things to get this done in time.  
 

  
 
 
 
 

 
 
 

 
 
 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-8601) agent should support rich data content negotiation

2018-08-24 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: agent should support rich data content negotiation   
 

  
 
 
 
 

 
 Henrik Lindberg You mentioned this week that you were going to update this ticket with some more about the possibilities of the rich data format I think? Maybe just the permutations or options that could occur.  
 

  
 
 
 
 

 
 
 

 
 
 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-8601) agent should support rich data content negotiation

2018-08-02 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8601  
 
 
  agent should support rich data content negotiation   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-8733) File type redefined when required in code

2018-05-15 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8733  
 
 
  File type redefined when required in code   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Affects Version/s: 
 SERVER 0.2.1  
 
 
Affects Version/s: 
 PUP 5.5.1  
 
 
Key: 
 SERVER PUP - 64 8733  
 
 
Project: 
 Puppet  Server  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-1952) Run specs against jruby

2018-04-23 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1952  
 
 
  Run specs against jruby   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-8591) [SPIKE] Investigate removing webrick

2018-04-16 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8591  
 
 
  [SPIKE] Investigate removing webrick   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-7407) Add deprecation warning to Puppet::Util.absolute_path?

2018-03-26 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 Is this on the table for Puppet 6?  
 

  
 
 
 
 

 
 
 

 
 
 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-8504) Emit deprecation warning for ruby 2.1 and 2.2

2018-03-19 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8504  
 
 
  Emit deprecation warning for ruby 2.1 and 2.2   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-6893) Remove Ruby 1.9.3 support

2018-03-19 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6893  
 
 
  Remove Ruby 1.9.3 support   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-6893) Remove Ruby 1.9.3 support

2018-03-19 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6893  
 
 
  Remove Ruby 1.9.3 support   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-8487) Eliminate use of MethodHelper

2018-03-15 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8487  
 
 
  Eliminate use of MethodHelper   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes: 
 Not Needed  
 
 
Fix Version/s: 
 PUP 5.5.1  
 
 
Fix Version/s: 
 PUP 6.0.0  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-03-13 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 It seems worth it to me. I don't like having it in one more place either but it would probably be pretty small.  
 

  
 
 
 
 

 
 
 

 
 
 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-8487) Eliminate use of MethodHelper

2018-03-09 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8487  
 
 
  Eliminate use of MethodHelper   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-8485) Cached failed confine lookups

2018-03-09 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8485  
 
 
  Cached failed confine lookups   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-03-09 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/scope.rb#L525-L544 If you're not in strict mode it doesn't fail. The exception gets caught here and turned into a warning, which I think is consistent with non-strict mode in general.  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-03-08 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 Coming back to this, it looks like it's the calls to lookupvar here that can fail without a catch https://github.com/puppetlabs/puppet/blob/master/lib/hiera/scope.rb#L23-L25      
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-02-27 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 Based on further conversation with Henrik outside of this ticket I think this can be fixed by adding a catch in our code somewhere so it doesn't fall back to raising an exception. I'm investigating.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
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-8486) Warning for undefined variables is slow in jruby

2018-02-26 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 I only found a couple places that either the throw or raise would be caught and it's not skipping any code paths, just returning a sentinel would work as well and not be as goto-like. It's possible I'm missing some cases though. It also seems like depending on the code path here the warning message is different for the same error.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
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-8487) Eliminate use of MethodHelper

2018-02-23 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8487  
 
 
  Eliminate use of MethodHelper   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/02/23 11:37 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 This serves no purpose but to obfuscate code and I've measured it as a significant source of garbage.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 
 

Jira (PUP-8486) Warning for undefined variables is slow in jruby

2018-02-22 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8486  
 
 
  Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/02/22 4:13 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 The use of exceptions here https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/scope.rb#L530-L543 when running in :warning mode (the default) is slow on JRuby. With a single undefined variable referenced in my hiera hierarchy I found handling this without exceptions resulted in a 20% runtime improvement. I suspect both the throw and the exceptions are unnecessary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  

Jira (PUP-8485) Cached failed confine lookups

2018-02-22 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8485  
 
 
  Cached failed confine lookups   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 Calls to confine for facts like  \ { { operatingsystem} }  end up trying to require a file  \ { { operatingsystem.rb} }  on every test before falling back to a fact value. Even a noop require is expensive and caching these negative lookups results in a significant reduction of garbage.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
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-8485) Cached failed confine lookups

2018-02-22 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8485  
 
 
  Cached failed confine lookups   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/02/22 4:07 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 Calls to confine for facts like {operatingsystem} end up trying to require a file {operatingsystem.rb} on every test before falling back to a fact value. Even a noop require is expensive and caching these negative lookups results in a significant reduction of garbage.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

   

Jira (BOLT-98) Add sudo and sudo password prompt support

2017-11-01 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle assigned an issue to Patrick Carlisle 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-98 
 
 
 
  Add sudo and sudo password prompt support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Assignee:
 
 Patrick Carlisle 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-98) Add sudo and sudo password prompt support

2017-11-01 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-98 
 
 
 
  Add sudo and sudo password prompt support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Sprint:
 
 Tasks  ELP (1.0)  Kanban 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-7979) Add a run_command() function

2017-09-28 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-7979 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a run_command() function  
 
 
 
 
 
 
 
 
 
 
I've changed the bolt executor methods to return a normal ruby Hash for results instead of Concurrent::Map. This should fix problems in consuming it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "cloud" fact that identifies Azure

2016-11-30 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "cloud" fact that identifies Azure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Sprint:
 
 Analytics 2016-10-19, Analytics 2016-11-02, Analytics 2016-11-16, Analytics 2016-11-30 , Analytics 2016-12-14 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "virtualization" fact that identifies AWS, Azure, etc

2016-11-02 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "virtualization" fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Sprint:
 
 Analytics 2016-10-19, Analytics 2016-11-02 , Analytics 2016-11-16 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "virtualization" fact that identifies AWS, Azure, etc

2016-10-19 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "virtualization" fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Sprint:
 
 Triage,  Analytics 2016-10-19 , Analytics 2016-11-02 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "virtualization" fact that identifies AWS, Azure, etc

2016-10-19 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "virtualization" fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Sprint:
 
 Triage, Analytics 2016-10-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "cloud" or similar fact that identifies AWS, Azure, etc

2016-10-05 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "cloud" or similar fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Sprint:
 
 Analytics 2016-10-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "cloud" or similar fact that identifies AWS, Azure, etc

2016-10-05 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "cloud" or similar fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "cloud" or similar fact that identifies AWS, Azure, etc

2016-10-05 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "cloud" or similar fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Team:
 
 Agent & Platform Analytics 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5744) Remove non-JSON safe default_literal objects from classes_per_environment response

2016-02-02 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-5744 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove non-JSON safe default_literal objects from classes_per_environment response  
 
 
 
 
 
 
 
 
 
 
yes, everything should recursively follow the rules or the whole thing is omitted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression

2016-01-19 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-5713 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_  
 
 
 
 
 
 
 
 
 
 
I expect to only have the default_source available in this case, if that's the question. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3438) Pass facts from catalog requests directly to node requests.

2015-12-31 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-3438 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pass facts from catalog requests directly to node requests.  
 
 
 
 
 
 
 
 
 
 
there's accidental behavior here, in that the caching that happens as a side effect masks other weirdness of the configurer bootstrapping an environment & facts 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5542) 'splay' seems broken

2015-12-16 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-5542 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 'splay' seems broken  
 
 
 
 
 
 
 
 
 
 
There is a scheduler that runs the agent in daemon mode, each scheduler is created with a splay initially and the splay is kept constant for a given agent daemon. If you look two lines above the splay config is fed into create_job, which creates a SplayJob if splay is true. In initialization it generates a splay and all runs for that daemon are offset by that amount. I'm guessing we didn't want to have a single agent vary in its run interval to avoid weirdness like running twice in 10 minutes followed by a 50 minute gap. 
Whether it actually works I can't comment on, but that's the intent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-4819) Add service for obtaining class information per environment

2015-07-15 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-4819 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add service for obtaining class information per environment  
 
 
 
 
 
 
 
 
 
 
Looks good. The plan is to expose this via http in clojure? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4747) resource_types response has AST for parameters' default values

2015-06-11 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-4747 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: resource_types response has AST for parameters' default values  
 
 
 
 
 
 
 
 
 
 
Steve Barlow Moses Mendoza Lindsey Smith 
This is a major SG regression for the node classifier. We will be unable to display default values correctly in the UI. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4747) resource_types response has AST for parameters' default values

2015-06-11 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4747 
 
 
 
  resource_types response has AST for parameters' default values  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Carlisle 
 
 
 

Priority:
 
 Normal Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3943) Make sure console.conf is under $confdir

2015-02-02 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-3943 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Make sure console.conf is under $confdir  
 
 
 
 
 
 
 
 
 
 
I think that file is from the old console, not pe-console-services. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3644) move all legacy and v2.0 endpoints to v3

2014-12-03 Thread Patrick Carlisle (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Carlisle commented on  PUP-3644 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: move all legacy and v2.0 endpoints to v3  
 
 
 
 
 
 
 
 
 
 
Pretty easy. I'm not sure if we have to care about backwards compatibility. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2870) sample auth.conf gives invalid syntax for deny

2014-06-30 Thread Patrick Carlisle (JIRA)
Title: Message Title










 

 Patrick Carlisle created an issue


















 Puppet /  PUP-2870



  sample auth.conf gives invalid syntax for deny 










Issue Type:

  Bug




Affects Versions:


 3.6.2




Assignee:


 Unassigned




Created:


 30/Jun/14 4:27 PM




Priority:

  Normal




Reporter:

 Patrick Carlisle










The sample auth.conf give deny [host|backreference|*|regex] as the syntax for deny, but using deny * gives me the error Error: Invalid pattern * at line 4 of }} (and the filename is missing from the error message). As far as I understand it {{deny * is redundant anyway.












   

 Add Comment






















   

Jira (PUP-2522) The transaction_uuid should be available to a node terminus

2014-05-11 Thread Patrick Carlisle (JIRA)
Title: Message Title










 

 Patrick Carlisle assigned an issue to Patrick Carlisle


















 Puppet /  PUP-2522



  The transaction_uuid should be available to a node terminus 










Change By:

 Patrick Carlisle




Assignee:

 PatrickCarlisle












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2522) The transaction_uuid should be available to a node terminus

2014-05-09 Thread Patrick Carlisle (JIRA)
Title: Message Title










 

 Patrick Carlisle created an issue


















 Puppet /  PUP-2522



  The transaction_uuid should be available to a node terminus 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 08/May/14 4:38 PM




Priority:

  Normal




Reporter:

 Patrick Carlisle










The id is passed into the catalog terminus but it doesn't go into the node query. It would be swell if it did.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 

Jira (PDB-565) Support trusted facts in PuppetDB fact storage

2014-04-18 Thread Patrick Carlisle (JIRA)
Title: Message Title










 

 Patrick Carlisle commented on an issue


















  Re: Support trusted facts in PuppetDB fact storage 










Lindsey Smith PO To clarify, the NC service does not use data from PuppetDB to make decisions. We'll need to use PuppetDB from the Console UI in order to show previews of NC changes and estimate current groups.












   

 Add Comment

























 PuppetDB /  PDB-565



  Support trusted facts in PuppetDB fact storage 







 Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.

Jira (PDB-565) Support trusted facts in PuppetDB fact storage

2014-04-01 Thread Patrick Carlisle (JIRA)
Title: Message Title










 

 Patrick Carlisle commented on an issue


















  Re: Support trusted facts in PuppetDB fact storage 










It's available on the node object as node.trusted_data after compilation has started. I'm not sure where you guys plug into that. I may have to do some work to reorder when it's initialized.












   

 Add Comment

























 PuppetDB /  PDB-565



  Support trusted facts in PuppetDB fact storage 







 Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, 

Jira (PUP-1632) Hack Day - 7 Feb 2014

2014-02-11 Thread Patrick Carlisle (JIRA)
Title: Message Title










 

 Patrick Carlisle commented on an issue


















  Re: Hack Day - 7 Feb 2014 










I intended to put some work into beaker to make NC work easier. I didn't get too far in this, most of my work went into the helper file within NC. I've satisfied our temporary need to run source puppet with packaged NC, but still have a lot of work to do.












   

 Add Comment

























 Puppet /  PUP-1632



  Hack Day - 7 Feb 2014 







 Please add a quick summary of your hack day here.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.