project.jobs close_reason support needed
See original GitHub issueI would like to get the last “finished” job for a spider.
But if I do:
project.jobs(spider='myspider', state='finished', count=-1)
I will only get jobs with a state of finished
but this may include jobs with a close_reason of shutdown
or something other than “finished”.
I would like to be able to do:
project.jobs(spider='myspider', close_reason='finished', count=-1)
which would of course assume that state is finished
as well.
Issue Analytics
- State:
- Created 10 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Project Support Jobs, Employment | Indeed.com
897642 Project Support jobs available on Indeed.com. Apply to Receptionist, Estimator Coordinator, Operations Coordinator and more!
Read more >Cool Careers | Wounded Warrior Project Job Openings
Cool Careers is the employment home of Wounded Warrior Project® (WWP). Search through our job openings, and join a family of dedicated, passionate...
Read more >Careers | The Nature Conservancy
Learn more about what it's like working here! Life Inside TNC · Your Career at TNC · Need Help Applying?
Read more >Search Jobs - Google Careers
Search, find and apply to job opportunities at Google. Bring your insight, imagination and healthy disregard for the impossible. Together, we can build...
Read more >Return to Work Program - Meta Careers
Throughout the 6-month program, they'll receive training, mentorship, and the support needed to be successful while solving complex, real-world problems.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the problem is that server side it will require a non-efficient scan on finished jobs. Although this is still more efficient than filtering client side, it is not as straightforward as we wish.
I think it is going to be client side filtering then.