fraul

I just came here to open an issue to thank the developers. Unsurprisingly, someone beat me to it. This is *awesome*. @nguyenquangminh0711 @gregoryfm @hieuk09 @qcam Thank you!!

Curious to see this issue, because we've noticed this behavior as well!

Here as well. Had it first on a previous version (can't remember), and then today when upgraded to 0.5.6205. Reverting back to 0.5.6101 fixed it, for now.

@wjordan You were right on Jordan! I missed that line during my investigation because it doesn't appear on every restart, but yes, it's there.

@wjordan I found this grepping the file, and confirmed they appeared during my phased restart tests with `fork_worker` ``` [2858] ! Terminating timed out worker: 9948 [2171] ! Terminating timed...

@h0jeZvgoxFepBQ2C That would not be the case, I have reproduced the bug waiting for the first deployment fully finishing to restart all 24 workers before issuing the second deployment.

@RipTheJacker is correct. Also, you can alias the keys for a better result. For instance: `User.left_joins(properties: :location).distinct.limit(100).pluck_h("users.id as users_id", "locations.city as city")` Returns an array of: `{"users_id"=>2, "city"=>"Curitiba"}` This way,...

@janko Janko, would you know how I could sharpening when using a `process resize_to_*` macro with Carrierwave?

Update: based on this comment https://github.com/pay-rails/pay/blob/73f53778ea2c411992d65380d4b38572f2faaa12/lib/pay/stripe.rb#L63-L67 I think the idea was to subscribe to `stripe.charge.succeeded` to capture charges BOTH from individual charges AND subscriptions. However, this is the list of...

Hi everyone, The docs (https://vuex.vuejs.org/guide/getters.html#property-style-access) still contain this warning:  Since this PR is closed, I think this is safe to remove now?