Ensure Processor::Cookie can run after Processor::RemoveCircularReferences #996
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
This commit seems to have introduced a bug: getsentry/raven-ruby@ad440b9
Processor::RemoveCircularReferencesreplaces elements of the event with the string(...), butProcessor::Cookies#generate_masked_cookiesassumes that its param implements#merge(Stringdoes not). Previously,Processor::Cookieswas not run inRaven::Event#async_json_processors.Unfortunately I wasn't able to get the test suite running locally (getting an error about requiringFixed!rails), so apologies if I've accidentally added a failing specImpact
This exception (
undefined method 'merge' for "(...)":String) would be rescued, but could cause a large number of events to be sent synchronously instead of asynchronously.