GODRIVER-3163 Preserve original cancellation/timeout errors. #1625
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.
GODRIVER-3163
Summary
Previously transformNetworkError() would replace original errors with either
context.Canceled
orcontext.DeadlineExceeded
. This changes that so that the original error information is preserved.Background & Motivation
Use of
errors.Is()
implies a desire to honor wrapped errors. Replacing a wrapped error withcontext.Canceled
subverts that.This subversion adversely affects Mongosync, which wraps
context.Canceled
with detail about the cancellation’s cause. (See REP-3632 for details about this.)The same pattern applies to discarding the driver’s
originalError
in favor of DeadlineExceeded. We can safely preserve the originalnet.Error
’s context by wrapping DeadlineExceeded.