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
fix(node): Skip capturing Hapi Boom error responses. #11151
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
size-limit report 📦
|
onurtemizkan
force-pushed
the
onur/hapi-skip-boom-responses
branch
4 times, most recently
from
March 21, 2024 13:40
762985d
to
9b45cec
Compare
onurtemizkan
force-pushed
the
onur/hapi-skip-boom-responses
branch
from
March 24, 2024 22:14
9b45cec
to
c671e1f
Compare
mydea
approved these changes
Mar 25, 2024
AbhiPrasad
changed the title
ref(node): Skip capturing Hapi Boom error responses.
fix(node): Skip capturing Hapi Boom error responses.
Mar 25, 2024
Closed
AbhiPrasad
pushed a commit
that referenced
this pull request
Mar 27, 2024
Resolves: #11069 After checking the behaviour, it seems to me that we don't need to capture any Boom responses, as the errors that may cause a `5xx` response are already captured by the core logic. To add an option to control this behaviour, we need to update the usage of `hapiErrorPlugin`, converting it to a function signature, which IMO may not worth doing, as I'm not sure if users in general would need to use it. This also adds `expectError()` to the `node-integration-tests` runner to allow `5xx` responses to be tested.
AbhiPrasad
pushed a commit
that referenced
this pull request
Mar 27, 2024
Resolves: #11069 After checking the behaviour, it seems to me that we don't need to capture any Boom responses, as the errors that may cause a `5xx` response are already captured by the core logic. To add an option to control this behaviour, we need to update the usage of `hapiErrorPlugin`, converting it to a function signature, which IMO may not worth doing, as I'm not sure if users in general would need to use it. This also adds `expectError()` to the `node-integration-tests` runner to allow `5xx` responses to be tested.
AbhiPrasad
added a commit
that referenced
this pull request
Mar 28, 2024
Backport of #11151 to v7 Co-authored-by: Onur Temizkan <onur@narval.co.uk>
cadesalaberry
pushed a commit
to cadesalaberry/sentry-javascript
that referenced
this pull request
Apr 19, 2024
Resolves: getsentry#11069 After checking the behaviour, it seems to me that we don't need to capture any Boom responses, as the errors that may cause a `5xx` response are already captured by the core logic. To add an option to control this behaviour, we need to update the usage of `hapiErrorPlugin`, converting it to a function signature, which IMO may not worth doing, as I'm not sure if users in general would need to use it. This also adds `expectError()` to the `node-integration-tests` runner to allow `5xx` responses to be tested.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves: #11069
After checking the behaviour, it seems to me that we don't need to capture any Boom responses, as the errors that may cause a
5xx
response are already captured by the core logic. To add an option to control this behaviour, we need to update the usage ofhapiErrorPlugin
, converting it to a function signature, which IMO may not worth doing, as I'm not sure if users in general would need to use it.This also adds
expectError()
to thenode-integration-tests
runner to allow5xx
responses to be tested.