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

Honeybadger possible severe impact on resque performance #1451

Closed
paneq opened this Issue Apr 18, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@paneq

paneq commented Apr 18, 2016

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.

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Apr 18, 2016

Member

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.

Member

steveklabnik commented Apr 18, 2016

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.

@chrisccerami

This comment has been minimized.

Show comment
Hide comment
@chrisccerami

chrisccerami Apr 18, 2016

Contributor

👍 That was great thinking @paneq.

Contributor

chrisccerami commented Apr 18, 2016

👍 That was great thinking @paneq.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment