Mastodon

0 posts0 participants0 posts today

Jan PeterkaI'm adding background jobs to my new app (Rails7.2 + SolidQueue), and not sure how things should be designed. I need to run daily job to generate notifications on user-created task due/reminder date.Should I:1) create one job that iterates all relevant tasks and generates notifications? (might get slow with more users)2) have one job that iterates tasks, and creates separate job for every relevant task?3) something else?<a href="https://ruby.social/tags/rubyonrails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rubyonrails</a> <a href="https://ruby.social/tags/activejob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#activejob</a> <a href="https://ruby.social/tags/SolidQueue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SolidQueue</a>

Honeybadger.ioSidekiq remains the fastest and most robust job processing system for Ruby on Rails and ActiveJob.Our latest article explores how to work with scheduled jobs in Sidekiq.Give it a read!<a href="https://www.honeybadger.io/blog/sidekiq-background-jobs/?utm_source=mastodon&utm_medium=social" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.honeybadger.io/blog/sidekiq-background-jobs/?utm_source=mastodon&utm_medium=social</a><a href="https://ruby.social/@sidekiq" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sidekiq</a> <a href="https://ruby.social/@getajobmike" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@getajobmike</a><a href="https://honeybadger.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ruby</a> <a href="https://honeybadger.social/tags/RubyOnRails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RubyOnRails</a> <a href="https://honeybadger.social/tags/Sidekiq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sidekiq</a> <a href="https://honeybadger.social/tags/ActiveJob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActiveJob</a> <a href="https://honeybadger.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a>

Honeybadger.ioPicture this: you're six months into a fresh Rails app that processes business-critical jobs with Solid Queue—and you deployed a bug that is wreaking havoc in thousands of jobs. How do you find them?You'll wish you'd read our latest article from Jeffery Morhous!<a href="https://www.honeybadger.io/blog/solid-queue-lifecycle/?utm_source=mastodon&utm_medium=social" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.honeybadger.io/blog/solid-queue-lifecycle/?utm_source=mastodon&utm_medium=social</a><a href="https://honeybadger.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ruby</a> <a href="https://honeybadger.social/tags/RubyOnRails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RubyOnRails</a> <a href="https://honeybadger.social/tags/SolidQueue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SolidQueue</a> <a href="https://honeybadger.social/tags/ActiveJob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActiveJob</a> <a href="https://honeybadger.social/tags/SQlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQlite</a>

GripNews🌖 Ruby on Rails 的 LiteStack 簡介 | AppSignal Blog ➤ Ruby on Rails 的 LiteStack 簡介 ✤ <a href="https://blog.appsignal.com/2023/09/27/an-introduction-to-litestack-for-ruby-on-rails.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.appsignal.com/2023/09/27/an-introduction-to-litestack-for-ruby-on-rails.html</a> 本文介紹 LiteStack，一個一站式解決方案，可在單臺機器上託管和處理所有生產數據。LiteStack 使用 SQLite 提供數據庫、ActiveJob、ActionCable 和 ActiveSupport::Cache 存儲。此外，本文還介紹了 Litestream 和 StableDiffusion，並提供了一個示例 Rails 應用程序。 + 這篇文章提供了很好的 LiteStack 簡介，並且還有一個有趣的示例應用程序。 + 很棒的文章，對於 Ruby on Rails <a href="https://mastodon.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ruby</a> on Rails <a href="https://mastodon.social/tags/LiteStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LiteStack</a> <a href="https://mastodon.social/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> <a href="https://mastodon.social/tags/ActiveJob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActiveJob</a> <a href="https://mastodon.social/tags/ActionCable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActionCable</a> <a href="https://mastodon.social/tags/LiteCache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LiteCache</a> <a href="https://mastodon.social/tags/Litestream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Litestream</a>

FastRuby.io🚀 Ruby upgrade tip: Fix those sneaky ArgumentErrors during your upgrade from Ruby 2 to Ruby 3. Francois breaks it down on the blog: <a href="https://www.fastruby.io/blog/custom-deprecation-behavior.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=safeguardingfromdeprecation&utm_content=Gif&utm_id=" rel="nofollow noopener noreferrer" target="_blank">https://www.fastruby.io/blog/custom-deprecation-behavior.html?utm_source=Mastodon&utm_medium=Organic&utm_campaign=Blogpromo&utm_term=safeguardingfromdeprecation&utm_content=Gif&utm_id=</a> <a href="https://ruby.social/tags/rubyonrails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rubyonrails</a> <a href="https://ruby.social/tags/railsupgrade" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#railsupgrade</a> <a href="https://ruby.social/tags/activejob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#activejob</a> <a href="https://ruby.social/tags/sidekiq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sidekiq</a>

masukomi<a href="https://connectified.com/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruby</a> geeks: I have been on a quest to test <a href="https://connectified.com/tags/Rails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rails</a>'s <a href="https://connectified.com/tags/ActiveJob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActiveJob</a> with <a href="https://connectified.com/tags/rspec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rspec</a>. I have found precisely zero official documentation that actually works. HERE IS THE ONLY GUIDE THAT HAS WORKED<a href="https://gist.github.com/ChuckJHardy/10f54fc567ba3bd4d6f1" rel="nofollow noopener noreferrer" target="_blank">https://gist.github.com/ChuckJHardy/10f54fc567ba3bd4d6f1</a>when / if you get errors about Minitest::UnexpectedError (even though you're running rspec) then read this SO post <a href="https://stackoverflow.com/questions/72674828/job-spec-wraps-error-with-minitestunexpectederror-after-rails-6-1-upgrade" rel="nofollow noopener noreferrer" target="_blank">https://stackoverflow.com/questions/72674828/job-spec-wraps-error-with-minitestunexpectederror-after-rails-6-1-upgrade</a>

masukomii've wasted over an hour on this take-home test because rspec's documentation AND ?!SOURCE?! do not match the reality i am seeing in ANY WAY. methods that only accept blocks and throw exceptions if you pass them something else are complaining that they've been passed a block. :lolsob: Testing <a href="https://connectified.com/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruby</a>'s <a href="https://connectified.com/tags/ActiveJob" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActiveJob</a> turns out to be a pain in the arse.

Recent searches

Search options

Administered by:

Server stats:

#activejob