Skip to content
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

Fixes a Fate bug (part 2) #4994

Merged
merged 1 commit into from
Oct 21, 2024
Merged

Conversation

kevinrr888
Copy link
Member

fixes an issue with how Fates WorkFinder handles InterruptedExceptions which can lead to an infinite error loop and leave the WorkFinder broken

I'm wondering if this is a problem elsewhere as there are many places that handle an InterruptedException the same way

} catch (InterruptedException e) {
    Thread.currentThread().interrupt();
    ...
}

The conversation which brought about this PR was from:
#4965

This PR in conjunction with #4965 close #4906

fixes an issue with how Fates WorkFinder handles InterruptedExceptions
which can lead to an infinite error loop and leave the WorkFinder broken
@kevinrr888 kevinrr888 added this to the 4.0.0 milestone Oct 17, 2024
@kevinrr888 kevinrr888 self-assigned this Oct 17, 2024
@kevinrr888 kevinrr888 mentioned this pull request Oct 17, 2024
@kevinrr888 kevinrr888 merged commit 9416715 into apache:main Oct 21, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make WorkFinder and the TransactionRunners critical to the Manager
2 participants