Recent searches
Search options
So, it's Feb 2025 and #Heroku apps using their heroku-20 stack starts to fail on builds, expected but I still don't like it.
We have only 17 apps with that, and very close to update them all to #ruby 3.x - the main reason why we are still in that stack. More info in the ALT text of the image below.
I think I'll share my progress here, and also if you have questions or something please do; been there, done that, bough the book, DVD, Blu Ray and 4K edition - and watched the musical at Broadway.
feb 06, 2025. We are down to 13 apps still using `heroku-20` stack.
The most difficult part so far are the problem with Sidekiq::Extensions::Delay** because we have very mucho `.delay` sprinkled here and there on our #ruby apps - yes, we still are in some Sidekiq 6.x
@esparta I can help perhaps? I wrote and maintain https://github.com/gemhome/sidekiq-delay_extensions and have upgraded our own images and versions
@esparta@ruby.social@hazula Hi Benjamin,
yes, we've been considering using sidekiq-delay_extensions for a while. There's a couple of points why we didn't immediately:
- the gem is using `unsafe_load` by default
- we want to move out of `.delay` if possible
in the first case, our security team flagged and prefer to use `safe_load` whenever is possible. I can file a issue where including our (very-naïve) monkey patch.
secondly, our code abuse .delay, and it's not uncommon to see kBs of data sent to redis :S
@esparta let me know how I can help. I thought I wrote it in a way to allow overriding it with this in mind.