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

Improve the Processor base class and SanitizePasswordsProcessor class#521

Open
htquach wants to merge 2 commits intogetsentry:masterfrom
htquach:master
Open

Improve the Processor base class and SanitizePasswordsProcessor class#521
htquach wants to merge 2 commits intogetsentry:masterfrom
htquach:master

Conversation

@htquach
Copy link
Copy Markdown

@htquach htquach commented Nov 4, 2014

Improve Processor to also check for stacktrace at the 'data' level. A stacktrace can exist in the data
even without an 'exception' key.
Also added 'pw' and 'cred' to the list of FIELDS to screen for in SanitizePasswordProcessor. These
two fields being used in the standard python LDAP module.

Improve Processor to also check for stacktrace at the 'data' level.  A stacktrace can exist in the data
even without an 'exception' key.
Also added 'pw' and 'cred' to the list of FIELDS to screen for in SanitizePasswordProcessor.  These
two fields being used in the standard python LDAP module
Comment thread raven/processors.py
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we have a test that highlight why this is needed ?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Are you asking for updating the tests/processors/tests.py for case when an event that has 'stacktrace' in its data? I have just updated the processor test to include the two additional 'pw' and 'cred' field. As for the test case for 'AUTO_LOG_STACKS', I will need to spend a bit more time in figuring how to write a test for that (turn on auto_log_stacks and build a raven.events.Message).

This can be reproduce when "auto_log_stacks" option is set to True and logging a Message event.

@ashwoods ashwoods self-assigned this Oct 11, 2017
@ashwoods ashwoods added this to the 6.3.0 milestone Oct 11, 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.

3 participants