chore(serverless): set ignoreSentryErrors to true by default #4994
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.
This PR is adding on top of the #4620 making
ignoreSentryErrors: true
by default.When rate limiting is enabled, users get 429s. Whenever they experience this, they fix/fallback into adding:
so they can get
ignoreSentryErrors: true
.Using our lambda layer and having
ignoreSentryErrors: true
by default will make their setup a working out-of-the-box solution:Fixes: #4949 #4582 #4799