fix(waitForFunction): handle predicate that throws #2488
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
Currently, we fail when the predicate throws on the first call, and timeout when it fails on any other call. There are two possible ways to handle throwing predicates: - Fail waitForFunction if predicate throws once. This is good since it gives you the error faster. - Tolerate predicate exceptions. This is good because you do not have to worry about non-initialized state during load. This change implements the former.
aslushnikov
approved these changes
Jun 8, 2020
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.
Currently, we fail when the predicate throws on the first call, and timeout when it fails on any other call.
There are two possible ways to handle throwing predicates:
This change implements the first way.