-
Notifications
You must be signed in to change notification settings - Fork 404
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
handle ignore_status_codes defined as strings #109
Conversation
return expect(urltils.isError(config, 401)).false; | ||
}); | ||
|
||
it("should handle ignore_status_codes defined as integers", function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was working before, just added one more test to make sure
Ah, this would explain a bug people have been seeing intermittently since the launch of the module. Good find! Thanks for passing this on! Because |
Good point. |
Hi, Pierre! Sorry for the delay, but this is now fixed in 7d3b835, which is part of v1.3.1 of the module, now on npm. Thanks for the report! |
👍 |
…/prisma-app/app/semver-6.3.1 chore(deps): bump semver from 6.3.0 to 6.3.1 in /prisma-app/app
…/protobufjs-7.2.4 Bump protobufjs from 7.2.3 to 7.2.4
…/urijs-1.19.9 Bump urijs from 1.19.8 to 1.19.9
updates the sns instrumentation based on the onResolved hook
updates the sns instrumentation based on the onResolved hook
This should solve the problem with
NEW_RELIC_ERROR_COLLECTOR_IGNORE_ERROR_CODES
not working as expected.For example, if you want to ignore in your 401 errors, and 404 errors, you can set:
and it should work with that change.