-
Notifications
You must be signed in to change notification settings - Fork 36
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
Ruby 3.0.1 ArgumentError #27
Comments
@shaundowling thanks for reporting. I'll have a look at this and fix it. It should take long to make cloudtasker 3.0-compatible. |
@alachaum np, thanks for the quick reply. It looked like it might be tricky depending on what backwards compatibility is required. This lib seems like the only serious game in town for running ruby on GCP so appreciate you guys open sourcing it 🙌 |
Hehe no worries. By the way, don't hesitate to checkout its little brother for Pub/Sub: https://github.com/keypup-io/cloudenvoy Any feedback appreciated there as well! (though we might have Rb3 compatibility issues on this project as well) |
cheers will take a look at that, currently looking into this as an activejob backend replacement for delayed job as the old pull worker approach doesn't really fit anymore. I'll roll back to 2.x and give it a try. |
@shaundowling feel free to play around with my branch on #32. The branch has I'm targeting |
Release candidate |
Hello
I'm trying to give this gem a whirl on ruby 3.0.1 using rails active job and receive an argument error when enqueuing a job.
I think it is related to the positional arguments changes detailed here.
I checked out the source and can confirm tests are green on 2.7.3 and red on 3.0.1
Is there any plan for 3.x support? I'm happy to pitch in to find a solution i'm just not sure where to start.
The text was updated successfully, but these errors were encountered: