Prevent unhandled rejections by stopping QueryManager more thoroughly. #4359
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 commit was extracted from #4337, since the problem it solves seems unrelated to that PR.
The
QueryManager#stop
method cancels all pending fetches by runningthis.fetchQueryRejectFns
. However, this leads to some unhandled promise rejections during tests, which might go unnoticed because they don't cause the test suite to fail.This commit makes the
QueryManager#stop
method a bit more aggressive about stopping active queries and unsubscribing from observables, which prevents the unhandled rejections.