Skip to content
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

airbrake-ruby: make sure optional filters are loaded #461

Merged
merged 1 commit into from
Mar 27, 2019

Conversation

kyrylo
Copy link
Contributor

@kyrylo kyrylo commented Mar 26, 2019

Fixes #460 (blacklist_keys config doesn't work)

The problem was that we never reconfigured already instantiated notifiers. We
always spawn notifiers as soon as the library is required but they get spawned
without some of default filters that are supposed to work given certain options
such as blacklist_keys.

The new #reset method respawns all notifiers on #configure. We have to
respawn so the new notifiers pickup the config. We need to spawn without the
user config so all the methods are working (e.g. notify returns a rejected
promise and such).

Fixes #460 (blacklist_keys config doesn't work)

The problem was that we never reconfigured already instantiated notifiers. We
always spawn notifiers as soon as the library is required but they get spawned
without some of default filters that are supposed to work given certain options
such as `blacklist_keys`.

The new `#reset` method respawns all notifiers on `#configure`. We have to
respawn so the new notifiers pickup the config. We need to spawn without the
user config so all the methods are working (e.g. notify returns a rejected
promise and such).
@kyrylo kyrylo force-pushed the 460-blacklist-filter-fix branch from 5a02641 to 9b55860 Compare March 26, 2019 21:41
@kyrylo kyrylo merged commit c822882 into master Mar 27, 2019
@kyrylo kyrylo deleted the 460-blacklist-filter-fix branch March 27, 2019 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant