You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dereuromark-queue has nice templates to see the jobs. Is this something we want to have in cakephp/queue and they just haven't been made or is it intentional to keep the scope just for making it easier to use queuing methods and not having stuff like that?
@kevindecapite I have ideas in mind but haven't gotten to any implementation and it might be quite some time until I do so. Anyone feel free to get started.
^ this is using Mark's
Steps I see to take:
I really like the Table schema from Mark's, so pulling from his migrations.
Then mostly from his templates. (See screenshot)
Something significantly more, but might be way scope creep, is having it auto-setup multiple queues so that one can have the "Abort".
Basically on the system running Cake: 1 queue sending the job, and 1 queue with other messages.
On the receiving side (for me it's Python): it ingests from the job queue, and also checks the other queue. If the other queue contains the job ID currently being run, it kills.
On the receiving side (for me it's Python): it ingests from the job queue, and also checks the other queue. If the other queue contains the job ID currently being run, it kills.
Would this be additional state that needs to be maintained by the Queue plugin?
No, but it would have a terminate() to set QueuedJobs table entry to failed => true, failure_message => User aborted. or similar.
Right now it doesn't seem possible to override the 'queue' field from the config in the Controller. I end up array_mergeing it in the Controller to make a new config and using that before sending the job.
Activity
markstory commentedon Feb 15, 2024
Having monitoring views/controllers sounds interesting to me. I don't think any have been added this far as nobody has brought it up.
umer936 commentedon Feb 15, 2024
Sweet. I'll do it then.
https://github.com/umer936/queue
https://github.com/dereuromark/cakephp-queue
I'll likely take huge inspiration from yours @dereuromark if that's ok (unless you'd prefer to do it/have your name on the commits)
dereuromark commentedon Feb 15, 2024
All good, glad it inspires people
kevindecapite commentedon Feb 19, 2024
@umer936 This would be a great value-add to the plugin. If I can contribute to what you're doing I'll certainly do so.
umer936 commentedon Mar 13, 2024
@kevindecapite I have ideas in mind but haven't gotten to any implementation and it might be quite some time until I do so. Anyone feel free to get started.
^ this is using Mark's
Steps I see to take:
Something significantly more, but might be way scope creep, is having it auto-setup multiple queues so that one can have the "Abort".
Basically on the system running Cake: 1 queue sending the job, and 1 queue with other messages.
On the receiving side (for me it's Python): it ingests from the job queue, and also checks the other queue. If the other queue contains the job ID currently being run, it kills.
markstory commentedon Mar 14, 2024
Would this be additional state that needs to be maintained by the
Queueplugin?umer936 commentedon Mar 14, 2024
No, but it would have a
terminate()to set QueuedJobs table entry to failed => true, failure_message => User aborted. or similar.Right now it doesn't seem possible to override the 'queue' field from the config in the Controller. I end up array_mergeing it in the Controller to make a new config and using that before sending the job.