search for: generifi

Hi all, I know this is a long shot, but could renaming the "Journey" module please be considered by those in a position to support it? I''ve written an issue on this in the journey repo also: https://github.com/rails/journey/issues/49 Essentially our project has a model named Journey, the same as Rails 3.2''s new routing driver. As a consequence we can no longer

Mostly surrounding if there are better(less hackish) ways of doing things. The first is the classic exported resource expiration problem. My existing modules use a wrapper that uses an inline template to call out to Ruby''s Time function, set a timestamp, and set the resource to absent after an expiration period, a cleanup script then runs on the database node and purges exported

Posted on stackoverflow but no traction yet: http://stackoverflow.com/questions/12942505/why-does-using-set-trace-func-work-in-some-places-but-cause-unexpected-return-l The following is a generified part of the code in a gem I''m working on: module SomeModule class << self attr_accessor :procedure def log_events(*args) args.flatten! if args.size == 1 eval "set_trace_func proc {|event, file, line, id, binding,...