I'm not supposed to use Que 0.x with Rails 6, am I?

[duartemvix]

I've been following all the guides and README's but I'm afraid Rails adapters on ActiveJob for Que still use a very old configuration for these libraries.

I've been getting basic errors such as No impilicit conversion of Time into String and it led me to think that's just so outdated that I couldn't even begin to fix it by myself.

I'm assuming all of you who's using it still uses Rails 4? Or Perhaps Rails 5?

[hlascelles]

It would be interesting to see the stack trace.

I can tell you that que-scheduler, which is built on que, performs an extremely wide matrix of tests, against many versions of Rails and que (including Rails 6). I would imagine it works fine in a production environment with Rails 6, but maybe there is a detail in the setup.

EDIT: After performing more tests, it seems that specs don't fully surface all the issues. Specifically, the Time conversion issue (#247) does crop up under full acceptance testing. I am going to mark Que 0.x/Rails 6 as "functional with patches" but unsupported in que-scheduler now.

[duartemvix]

It would be interesting to see the stack trace.

I can tell you that que-scheduler, which is built on que, performs an extremely wide matrix of tests, against many versions of Rails and que (including Rails 6). I would imagine it works fine in a production environment with Rails 6, but maybe there is a detail in the setup.

I already solved that reading through another issue. It was related to the way ActiveJob send arguments to Que and how they were coming in a different format than what Que could take.

All my doubts were not entirely solved however. I was looking to replace Sidekiq on a Heroku app with a library like Que that could run jobs on the same process and be more efficient than Rails' in memory asynchronous jobs. Can you clarify if it's possible to run Que as the same process of my app on this Heroku dyno?

[trende-jp]

@duartemvix Would you mind elaborating on the formatting issue? What did you do to solve the Time to String error?

It looks like this will probably work for my team:
#247 (comment)

[duartemvix]

@duartemvix Would you mind elaborating on the formatting issue? What did you do to solve the Time to String error?

It looks like this will probably work for my team:
#247 (comment)

That's the solution I used indeed.

I was having further problems trying to run a Que server simultaneously with a web process in Heroku but things are going fine at this moment. Apparently I couldn't even run Async jobs with Que I remember and what I did was putting aside this library in favor of Rails' async.