Skip to content
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.

Issues: albrow/jobs

16 Open 13 Closed
16 Open 13 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Job status is changed to executing but job has not started execution
#44 opened Sep 15, 2017 by paritosh90
Support environmental prefix
#42 opened Feb 14, 2017 by yadvendar
super slow help wanted performance
#41 opened Jul 10, 2016 by cypriss
1
Application can't start due to error which message is 'jobs: In scanJob: Could not find Type with name = %s'
#40 opened Apr 29, 2016 by fangjianwei
1
Error Handling?
#39 opened Mar 3, 2016 by pyrossh
5
FindById and job identifiers/human names
#31 opened Aug 27, 2015 by utrack
6
Job runtime error messages should include a stack trace enhancement
#25 opened May 29, 2015 by epelc
Panic in xen container
#24 opened May 29, 2015 by fzerorubigd
4
Reschedule with freq enhancement
#17 opened May 18, 2015 by epelc Version 0.5.0
2
Support redis sentinel enhancement question
#15 opened May 15, 2015 by epelc
6
Use an interface for jobs instead of a non-type-safe handler function (would break backwards-compatibility) enhancement question
#14 opened May 15, 2015 by albrow
4
Make database/storage pluggable after 1.0 enhancement
#9 opened Apr 18, 2015 by metakeule
6
Intercept UNIX signals enhancement
#7 opened Apr 15, 2015 by albrow Version 0.5.0
4
Find a better way to purge stale pools and re-queue stale jobs enhancement help wanted
#6 opened Apr 15, 2015 by albrow
2
Implement spread out retries enhancement
#4 opened Apr 15, 2015 by albrow
6
Use sets instead of sorted sets where appropriate enhancement
#3 opened Apr 15, 2015 by albrow
ProTip! Follow long discussions with comments:>50.