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.
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
feat: fallback to NoopProvider if we run into OOM [2/3] #483
feat: fallback to NoopProvider if we run into OOM [2/3] #483
Changes from all commits
29ec13b
b6fb255
8b6d93d
5491ea2
956193b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It doesn't every look like anything is using this rejection. If so, maybe it should be removed?
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.
@tgolen I think no, it's better to have it here
The function
tryOrDegradePerformance
just acts as an interceptor - it simply executes the function and in case of a specific exception just substitutes a provider. And when we develop such generic functions it's important to propagate exceptions further.And this function keeps full backward compatibility - if
getItem
or any other function would throw exception before, then it would be thrown further (and potentially we may have a code that handles these errors). So I'd like to keep this line and propagate exceptions and don't silently swallow them.