Alex Vondrak

What a fantastic article! It speaks to my soul. :sob: I definitely want to link it in the docs, at least. Thanks so much for forwarding it! And thanks @adam-p...

> (An answer I can see being possible is: Instead of looking through a list of headers names in order of preference, you go through the actual headers and take...

> Do you treat the latter two like a comma-separated list? (I think you do, but I have never tried to read Elixir.) They shouldn't be, but I guess there's...

@halostatue Thanks for the thorough breakdown in https://github.com/ajvondrak/remote_ip/issues/29#issuecomment-1094506433 :purple_heart: It'd be interesting to offer all these different strategies. This library was always pretty opinionated about the algorithm, although everything else...

I can reproduce this locally using a `MULTI` call on the same Redis connection from an enqueue hook, as noted in the discussion: ```ruby require "bundler/inline" gemfile do source "https://rubygems.org"...

This looks like yet another issue caused by https://github.com/resque/resque-scheduler/pull/767, because it tries to wrap all the enqueues done by resque-scheduler in a `MULTI`/`EXEC` transaction. Circa Redis 4.x, this means the...

> However, it's unclear to me what the interaction will be between two "top level" calls to these transaction commands. I.e., will the futures fire with the desired timing, or...

No forks I'm afraid, but the mitigations I see: 1. Lock to earlier versions resque-scheduler or redis so that you don't get this unfavorable interaction. Not ideal, but it's where...

Nice. Hugops and will be curious to see to any other tweaks you have lying around. :) Now that I'm spooling context back up on option 3 (credit to [this...

FWIW, I ran the repro script above against Rails 7.1.4, and while one of the tests was fixed, the other one involving supermethods is still broken: ``` $ ruby tests.rb...