Closed frbry closed 6 years ago
Hi @g3rd, any chance you could take a look at this one? Thanks! :)
Hi @g3rd, any feedback?
@frbry Sorry for the slow reply on this. At a high level this looks good. Going to pull this down and check it out, but I expect this will be merged soon.
Thanks for thinking of this!
@oudeismetis, I've created PR #22 to merge @frbry's work into the project as there were minor issues related to the introduction of cron jobs.
@frbry thank you again for the contribution! Given the merge conflict, we are looking to merge #22 to bring this feature in. Once that is merged I'll close this PR.
Thanks @oudeismetis and @tom-price!
Currently all scheduled and repeatable tasks are created with
result_ttl=-1
. This causesResult will never expire, clean up result key manually
warnings to be logged, which can be annoying.This PR creates a new field in
BaseTask
model so the user has the ability to changeresult_ttl
value for newly created RQ tasks.Note:
result_ttl
defaults to -1, which is weird because the RQ docs say it's 500 seconds by default: http://python-rq.org/docs/results/