Puppet Labs

09/07/2010

10:44 pm Puppet Dashboard Feature #4529 (Accepted): Commits should be emailed to a mailing list

Talking in person with Igal we think creating a dashboard-commits@puppetlabs.com mailing list and automating the send...

09/03/2010

10:39 pm Puppet Bug #4660 (Ready for Testing): Autotest failures

Clearing out the ARGV before loading puppet code seems like the best, easiest option to me. I'll post the diff to th...

09:18 pm Puppet Bug #4633: Array flattening breaks idempotence

Note, rejected in favor of #4638

09/02/2010

12:55 am Puppet Bug #4660: Autotest failures

Ticket #4308 didn't cause this (in fact it looks like #4308 never made it into the 2.6.x branch). It was caused by #...

12:51 am Puppet Refactor #4308 (Re-opened): Remove puppettest from spec_helper

Hey James,
I'm not seeing the SHA1 you mentioned in any branch. Did this actually get pushed?
Also in #4660 yo...

08/21/2010

08:07 pm Puppet Revision 3df0490c9dbc59e27869e09864177536400a5ae3: [#4298] Puppet apply prints an error if the fi...

Also warns you it's skipping files if you pass it more than one file to
apply.
Reviewed-by: Nick Lewis <nick@puppetl...

08/17/2010

06:52 pm Puppet Dashboard Feature #4553 (Needs design decision): Either add documentation on rotating logs or make it default

On Mon, Aug 16, 2010 at 3:32 PM, Steven L. Seed <slseed1969@gmail.com> wrote:
> I found the root cause of my problem...

08/13/2010

04:45 pm Puppet Dashboard Bug #4470: Documentation should explain how to prune reports, and task should prune correct reports

I sent a reply to this ticket in email, but the ticket hasn't updated in the last 5 minutes and I realized that the r...

04:09 pm Puppet Dashboard Bug #3298 (Ready for Checkin): reports.report datatype leads to data loss

+1

08/12/2010

11:50 pm Puppet Dashboard Bug #4470 (Ready for Testing): Documentation should explain how to prune reports, and task should...

New commit on the end of the branch with the changes.
I had already backticked things in another commit.
rake r...