Issues: resque/resque
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Ideas how on to health check the ec2 that hosts resque workers
#1797
opened Apr 3, 2022 by
454400098
The term_child_signal accessor does not appear to be used anywhere
#1793
opened Mar 7, 2022 by
matthewhively
Conflicting hooks between Resque and ActiveJob (e.g. before_enqueue)
#1787
opened Jan 19, 2022 by
hector
SIGABRT (signal 6) after a job is killed by the Linux OOM killer
#1783
opened Dec 22, 2021 by
rs-mfurlender
"Stack level too deep" when passing calling Resque.enqueue after_create
#1777
opened Nov 22, 2021 by
al3rez
PIDFILE contains only a single PID after starting multiple workers
#1721
opened May 14, 2020 by
z0marlin
retry and remove, could use some distance
good first issue
help wanted
#1719
opened Apr 17, 2020 by
danlo
Previous Next
ProTip!
Exclude everything labeled
bug with -label:bug.

