Wondering how long it’ll be until we can take advantage of the new async stuff coming up in Ruby.
There is quite a lot of plumbing, not just in Rails, but also in Ruby libraries and the ecosystem, that will need to become Ractor-compatible. It’s exciting times.
…that being said, I’m curious what kind of workload you’re looking forward to Ractors fo? I’ve found Rails multi-threading to be stable and performant for my background processing needs which are primarily bottlenecked on Database and network IO.
I’m looking forward to Ractors because I have little confidence that most gems and my own code are truly thread safe.
file encodes added the active job label . I could not even move the patch to the RSpec config. around the block, it works only right here, in the test. This issue showed up for us because we use the: sidekick adapter this problem did not occur in Rails 5.2. 3 , but began when I upgraded to
Did you have a fix on this issue? I have the same problem with Facing same issue but no response from anyone and couldnt find this topic troubleshooting in google.