Benjamin Fleischer

I've recently published my script hackage that mostly uses the v3 api, with the intention of improving design, usability, and testing.. but it works for what I was using it...

re: the issue, I just meant it would be good to foster an official fork and add a few maintainers or just specify it as dead, but you're open to...

I thought that 'on' could be useful for organizational purposes, e.g. db/triggers/${table_name}/${trigger_name}.sql but otherwise, perhaps we should make a PR to remove it since it's not used?

Anything you need from me?

I was just hacking the gem for the feature in this PR. I'm happy to take it over if OP @sobrinho is taking a break. Basic impl looks good to...

I'm happy to take this over if it's gonna be stale much longer. I've added some work arounds in my app, but I'd like to use it :)

I'm curious how this relates to crono. Once crono schedules my job, my job is responsible for how it rescues itself, no?

Yup. It's a bug ```ruby Crack::JSON.convert_json_to_yaml strj => "{\"budget_start\":!!timestamp \"2014-02-28\", \"budget_end\"!!timestamp \"2014-02-20\"}" ```

fwiw, the way I'm handling it now for consistency ```ruby included do attr_accessor :handled_db_validates_uniqueness end # see https://github.com/Shopify/activerecord-rescue_from_duplicate/issues/21 def save!(...) super rescue ActiveRecord::RecordNotSaved if handled_db_validates_uniqueness raise handled_db_validates_uniqueness else raise end...

https://github.com/apotonick/apotomo/blob/master/lib/apotomo/rails/view_helper.rb you can set the css element id yourself: ``` def widget_div(options={}, &block) options.reverse_merge!(:id => widget_id) ``` e.g. ``` widget_div(:id => 'something-unique') do ```