similar to: Announce: Puppet 3.0.2-rc3 available

in the spirit of minimal-impact ''leave no trace'' principles, this patch adds a missing feature, the ability to remove cookies. usage: @cookies.redbean = nil a side note, the trunk seems to be broken when using Markaby. i''ve tested this out using ngrep and firefox and opera w/ controllers that just return strings in any case.. -------------- next part --------------

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package

Hi, I wanted to use wxSugar enumerable features to add a method for returning checked items'' index to the CheckListBox class : require ''wx_sugar/version'' require ''wx_sugar/wx_classes/control_with_items'' require ''wx_sugar/wx_classes/listctrl'' class Wx::CheckListBox def checked_items # use of find_all method from Enumerable

Hello, First off, nice improvements hemant! Thanks for all the hard work. I just whipped up a new worker for a scheduled job that sends digest emails. Very smooth. However, moving some of my old backgroundrb into new backgroundrb isn''t going quite as smoothly. I have a import worker that takes a number of parameters and then is started dynamically. Here''s the a

Hello! I've been trying to implement a simple compiler from Scheme to LLVM IR, and have run into the following problem: In Scheme, any function can be called on any number of arguments, but it should check at runtime for arity errors. I haven't been able to find a way in LLVM IR to access the actual number of parameters a function was called with. I think the following approach might

I haven''t debugged this enough to understand what is happening, but I observe the following: someipset = bitmap:ip,mac 1) br0:+someipset 2) br0:+someipset[2] The first 1) doesn''t match anything in rules or tcrules, the second 2) matches fine. (Also using +someipset[1] doesn''t match anything) Is it possible/sensible/feasible to have shorewall figure out the

Hi, In my backend I need to know the arity of the callee at each safe point and export it in the .s file. This is needed for properly creating stack descriptors for the calls. I could easily implement that in the frontend for direct function calls but not for indirect calls (through register). Is there a way to do that with the current infrastructure? For example, I tried adding some metadata to

I started working on this in response to Dave Thomas'' keynote as RailsConf 2006. This little patch will validate that your text fields will fit into the database. Obviously this is just a start, and many more validations could be added. Also, this code could probably be extracted into a plugin instead of patch to ActiveRecord. Index: test/validations_test.rb

Hi all It''s been a while since we introduced our professional services team to the community. They lurk on the list quite a bit and help answer questions and queries (their elite skills are also available for hire!). They are (in alphabetical order): Dan Bode (dan@puppetlabs.com) Hunter Haugen (hunter@puppetlabs.com) Cody Herriges (cody@puppetlabs.com) Garrett Honeycutt

On Apr 16, 2008, at 2:50 AM, heisenbug wrote: > > And now here is my educated speculation: > There are 2 things that became slower > 1) Use::getUser() > 2) Use::get/set due to tagging. > > The former is seldom called: > > $ find lib -name "*.cpp" | xargs grep "getUser(" | wc -l > 41 The majority of those aren't actually Use::getUser, but

Puppet 3.0.1-rc1 is a bugfix release candidate for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328 Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.1-rc1.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available

Puppet 3.0.1 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328. This release contains contributions from the following people: Andrew Parker, Jeff McCune, Josh Cooper, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Niels Abspoel, Patrick

I have a mock of an instance of a class which descends from Array: class ArrayDescendent < Array; end #... in the specs... @descendent = mock ArrayDescendent How would I stub out ArrayDescendent#each, which is inherited from Array, to return multiple values successively? I could use and_yield, but that is raising an arity error (the anonymous function/ block should expect only *one

On Apr 16, 2:13 am, Dan Gohman <goh... at apple.com> wrote: > Hi Gabor, > > Can you provide performance data for this? I'd > like to know what affect these changes have on > compile time. Hi Dan, Unfortunately, no. I can feed you with some speculation, though, see below. The reason why I cannot do measurements (at the moment) is that - I have no experience with

Hi Peter, > Are there any better ways to solve this? Does any of the existing > calling conventions support this? Can't you handle this entirely in the front-end? Just decide by fiat that all of your scheme functions will take an extra (hidden to the Scheme users) parameter saying how many args they were given. That's how C++ deals with the implicit "this" parameter for

> Can't you handle this entirely in the front-end? Just decide by fiat > that all of your scheme functions will take an extra (hidden to the > Scheme users) parameter saying how many args they were given. That's > how C++ deals with the implicit "this" parameter for class methods. > Then you could either use varargs or bitcast your functions to a > reasonable

the man page for relational operators (see, e.g., ?'<') says: " Binary operators which allow the comparison of values in atomic vectors. Arguments: x, y: atomic vectors, symbols, calls, or other objects for which methods have been written. " it is somewhat surprizing that the following works: '<'(1) # logical(0) '<'() #

the man page for relational operators (see, e.g., ?'<') says: " Binary operators which allow the comparison of values in atomic vectors. Arguments: x, y: atomic vectors, symbols, calls, or other objects for which methods have been written. " it is somewhat surprizing that the following works: '<'(1) # logical(0) '<'() #

I found that scoped_access does not re-evaluate the filters on every run. If you are filtering access based on parameters, this can be bad. The scope is set on the first request and then further requests use the last generated scoping. The initial part of ScopedAccess::Filter#before looks like this: @scoping = controller.instance_eval(@scoping.to_s) if @scoping.is_a?(Symbol) This makes

URLS http://rubyforge.org/projects/codeforpeople/ http://codeforpeople.com/lib/ruby/traits INSTALL yes|sudo gem install traits ABOUT traits.rb is set of attr_* like methods on steroids, caffeine, and botox. it encourages better living through meta-programming and uniform access priciples. traits.rb supports smart inheritence of class attributes and a fistful of hooks for