-
Notifications
You must be signed in to change notification settings - Fork 57
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
Dashboard exception: Solid Queue::job is missing a status
method
#123
Comments
Hey @luigi7up, thanks for the report! What version of Solid Queue are you running? |
Hi Rosa, I'm not at home right now, but since I'm bundling it without a
version lock and with Rails 7.1... I assume it's the latest. I can confirm
in a couple of hours.
Thank you
…On Wed, May 22, 2024, 20:20 Rosa Gutierrez ***@***.***> wrote:
Hey @luigi7up <https://github.com/luigi7up>, thanks for the report! What
version of Solid Queue are you running?
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEUY65VPM4P5HFVXZI56TTZDTOV5AVCNFSM6AAAAABIEE7ZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGQ3DQNJZGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @rosa I just checked and the version is |
Ahhh! Could you try upgrading to the last version? 0.3.1 as of now. |
Yes, I did and it solved the problem. Thank you so much for such a swift
answer!
Best regards
Luka
…On Thu, May 23, 2024 at 10:49 AM Rosa Gutierrez ***@***.***> wrote:
Ahhh! Could you try upgrading to the last version? 0.3.1 as of now.
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEUY66YUPPK4NUSR2AWPOTZDWUR3AVCNFSM6AAAAABIEE7ZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGU3DSOBZG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@rosa Hi, I found another bug / exception that happens when I go to Failed Jobs and decide to discard a failed job. It fails to remove it with the following exception:
Do you prefer if I opened another issue for it? |
Oh! You need to copy and run the pending migration for Solid Queue, to create the
And then run the migrations. |
Thanks for the tip! I'll run the migrations. I'd expect Rails to tell me
about the pending migrations, but I guess these are Gem specific...
Again, thanks for your help
…On Thu, May 23, 2024, 16:50 Rosa Gutierrez ***@***.***> wrote:
Oh! You need to copy and run the pending migration for Solid Queue, to
create the solid_queue_recurring_executions table. In your app run:
bin/rails solid_queue:install:migrations
And then run the migrations.
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEUY6YI7Y5W3PBYLNESPQ3ZDX6ZXAVCNFSM6AAAAABIEE7ZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXGMZTCNRQHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@luigi7up, was this one solved for you after running the migrations? |
Yes, it was. Sorry for not providing any update. I'm running the jobs like
crazy in production :)
The whole idea of having queuing system that uses the same DB is just great.
Thank you so much!
…On Fri, Jun 7, 2024, 17:24 Rosa Gutierrez ***@***.***> wrote:
@luigi7up <https://github.com/luigi7up>, was this one solved for you
after running the migrations?
—
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEUY6ZJOQA7GUZ34IQ7SULZGHGC7AVCNFSM6AAAAABIEE7ZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGA3DENBVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
When I open Queues and click on a job that did not run because of an exception or because I pass wrong args I get the following error and the dashboard fails with a fatal exception
When I analyse the logs this is the error I see that the Solid Queue::job is missing a
status
methodI'm using Rails 7.1 with mission_control-jobs (~> 0.2.1) and everything is running in a Puma 6.0
The text was updated successfully, but these errors were encountered: