-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with v3.3.0, The property 'args' is not defined for Que::Scheduler::EnqueuedJobType #175
Comments
Interesting. Agreed, it looks like it should work as
More of the stack trace might help too... I am going to guess this is a serialisation issue where the tests are using symbols, but a roundtrip to the DB is returning strings. That area of code has changed in multiple places over the years, both inside Thank you for raising this. |
Ah, unfortunately. I dont have the stack trace anymore and I'm rushing a project right now to help revert the project to the previous state in which I found the bug in.
I've also tried the custom name method with class and args defined. (even purposely putting an args to the job) Off the top of my head, the tracestack I remember pointed to Hashie::Dash. I assume that there might be some issue with the parsing there. I'll try to see if I can find some time to dig deeper into this. Thank a lot mate! |
The way args are handled has been changed very slightly in 3.4.0 (support for hashes and nils was added). I'd be interested to hear if you see any difference or improvement. |
I've ran into this issue as well when upgrading to v3.4.0 with que v0.14.3
|
Gem 3.4.1 released. |
Hello,
I've been trying to run que-scheduler and I ran into this issue
This is following the same instructions on the Readme.
I've tried adding arguments purposely to the jobs and inside que_schedule.yml
I dug into the code and noticed this
Args are defined but somehow the scheduler when creating the job, cant seem to add the arguments to the class. Possibly from
args: data.fetch(:arguments)
(to_enqueue.rb)The fix I've done was to revert back to 3.2.8 and then everything was working again.
The text was updated successfully, but these errors were encountered: