GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
This is not exactly resque bug and you can close it immediately as resque developers cannot do anything to prevent it from happening. But I wanted people searching resque issues list to be able to find this problem easier in the future.
Awesome, great story! Well done.
Since it's not a real bug, I'm going to give it a close, but thanks for filing the issue; I hope it helps others in the future.
👍 That was great thinking @paneq.