Christian Schmidt

I suspect that calling `check_all_pending!` will cause random errors as those reported here: - https://stackoverflow.com/questions/73109620/getting-intermittent-error-of-no-connection-pool-for-activerecordbase-found - https://stackoverflow.com/questions/66774339/activerecordconnectionnotestablished-randomly-occured-in-deployed-instance-aft/66928112 The problem is hard to reproduce, but it seem to have gone away...

> So it appears like this would also fix the issue of a static GIF image always being processed according to the media limits as if it was an animated...

@ClearlyClaire I am not sure, what you are suggesting. Do you think we should convert them to a different animated image format (e.g. animated PNG) or to a static image?...

> I'm suggesting the animations are kept as animated PNGs. I don't know the history behind why we currently convert GIFs to mp4 instead of animated PNG, and I don't...

You are right; these changes cannot be committed in bulk. However, I still think the overall idea has some merit. The tools may be a useful for translators to point...

You should also pass add `**kwargs` to the method generated dynamically by `handle_asynchronously`: https://github.com/collectiveidea/delayed_job/blob/b66bb64437a8606a414a390531ac73108911434e/lib/delayed/message_sending.rb#L39-L50

I use this in production: ```ruby define_method(with_method) do |*args, **kwargs| curr_opts = opts.clone curr_opts.each_key do |key| next unless (val = curr_opts[key]).is_a?(Proc) curr_opts[key] = if val.arity == 1 val.call(self) else val.call...

A new switch, `--force_kill_waittime`, has been added to Daemons in https://github.com/thuehlinger/daemons/pull/65 (not yet released).

The new `--force_kill_waittime` switch for Daemons is included in the recent [1.3 release](https://github.com/thuehlinger/daemons/releases/tag/v1.3.0).

@jrichy1 I don't understand what you mean. Where exactly are you tagged?