-
Notifications
You must be signed in to change notification settings - Fork 638
[ISSUE #3830] InterruptedExceptions should not be ignored in the code. #4791
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
88dd059
[ISSUE #3830] InterruptedExceptions should not be ignored in the code.
5fa0c10
[ISSUE #3830] fix code style
58651cf
[ISSUE #3830] delete Unneeded throw
jevinjiang 2bc1de4
[ISSUE #3830] rethrown InterruptedException
jevinjiang ab06b18
[ISSUE #3830] InterruptedException return new SendResult
jevinjiang 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
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.
Since you have chosen to re-interrupt, is there no need to throw an exception again? Moreover, the throws are all non-
InterruptedException
s.既然您选择了重新中断是不是就没必要再抛异常了?更何况抛出都是一些非
InterruptedException
。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.
If I don't throw an exception, I will return a SendResult, so I chose to throw a StorageRuntimeException. Is there any better way? I can continue to modify it. 不抛出异常的话,就要返回一个SendResult,所以我选择了抛出一个StorageRuntimeException, 还有什么更好的做法没,我可以继续修改
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.
I think you can either return an empty
SendResult
, or you can use the other way of handlingInterruptedException
mentioned in the issue, "InterruptedExceptions should either be rethrown - immediately...".我觉得您可以返回空的
SendResult
,或者采用issue中提到的另一中处理InterruptedException
的方式“直接抛出中断异常”。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.
Okay, it's done. Thank you for your guidance in helping me complete the first issue。 已经修改完毕,感谢您帮我完成第一个issue。