-
Notifications
You must be signed in to change notification settings - Fork 392
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
[REQUEST] Start depending on airbrake-ruby 4.2.2? #941
Comments
Hi, yeah, that's the plan. Thanks for pinging, I actually forgot that this gem was locked to 4.1. I'll release a new version today. |
Small update. There are some complexities with upgrading, so I need a bit more time. Sorry for the false information. |
kyrylo
added a commit
that referenced
this issue
Mar 29, 2019
Fixes #941 ([REQUEST] Start depending on airbrake-ruby 4.2.2?)
Thanks for the update @kyrylo 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Airbrake config
Description
Hey guys, first of all, thank you for this amazing gem!
I did the setup and tried sending some test notifications.
The problem is that my
blacklist_keys
are not taken into account and every password appears in clear in the errors reporting tool (I'm using Errbit).I think it's a known issue that was fixed in this PR in airbrake-ruby dependency.
This fix was released in airbrake-ruby 4.2.2 but aibrake depends on airbrake-ruby 4.1.
Do you think it's possible to move on to the latest version of airbrake-ruby?
Any help would be greatly appreciated.
François
The text was updated successfully, but these errors were encountered: