Skip to content
This repository was archived by the owner on Oct 23, 2023. It is now read-only.

Conversation

@mpistrang
Copy link

@mpistrang mpistrang commented Feb 17, 2017

This change will allow the celery logging signal to recognize subclasses of raven.handlers.logging.SentryHandler when searching for existing handlers to add a CeleryFilter to, instead of adding a second handler. This resolves #961

@mpistrang mpistrang changed the title Allow subclasses of SentryHandler to be modified by the celery logging signal Allow subclasses of SentryHandler to be modified by the celery logging signal, resolves 961 Feb 17, 2017
@mpistrang mpistrang changed the title Allow subclasses of SentryHandler to be modified by the celery logging signal, resolves 961 Allow subclasses of SentryHandler to be modified by the celery logging signal, resolves #961 Feb 17, 2017
Copy link

@jcronyn jcronyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

Copy link
Contributor

@ashwoods ashwoods left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thx!

@mpistrang
Copy link
Author

Thanks @ashwoods for the approval. Do you need anything else from me for this to be merged?

@ashwoods
Copy link
Contributor

Just wanted to manually rebase it and run the tests again locally. will merge tomorrow morning.

@ashwoods ashwoods merged commit 4c59089 into getsentry:master Dec 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

raven.contrib.celery.register_logger_signal ignores subclasses of SentryHandler

3 participants