-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix(gax): do not treat a SocketTimeoutException as a thread interrupt #14578
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
Open
markaddleman
wants to merge
1
commit into
googleapis:main
Choose a base branch
from
markaddleman:fix/gax-socket-timeout-not-interrupt
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
In
testInterruptedIOExceptionStillFailsAsInterrupted, the test asserts thatfuture.get()throws anExecutionExceptionwith anInterruptedExceptionas its cause. However, becauseDirectRetryingExecutor.submitcallsThread.currentThread().interrupt(), the current thread's interrupt flag is set.If the interrupt flag is correctly preserved, any subsequent blocking call to
future.get()(which delegates to Guava'sAbstractFuture.get()) should immediately throw a standaloneInterruptedExceptionrather than anExecutionExceptionwrapping it, unless the interrupt flag was somehow cleared and lost during the future's completion callback execution.To ensure that the thread's interrupted status is correctly preserved and not lost, we should explicitly assert that the current thread remains interrupted after
runRetryingTimeoutscompletes, and then clear the flag. If the flag is currently being lost, we should investigate why and fix the underlying issue.References