-
Notifications
You must be signed in to change notification settings - Fork 411
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
fix a bug that ExchangeReceiver can't be canceled #4441
Conversation
Signed-off-by: bestwoody <[email protected]>
Signed-off-by: bestwoody <[email protected]>
…ugfix_cancel_recv
Signed-off-by: bestwoody <[email protected]>
Signed-off-by: bestwoody <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
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.
LGTM
if (!setEndState(ExchangeReceiverState::CANCELED)) | ||
return; |
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 (!setEndState(ExchangeReceiverState::CANCELED)) | |
return; | |
setEndState(ExchangeReceiverState::CANCELED); |
it's ok for finishing a queue twice.
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.
updated
{ | ||
assert(new_state == ExchangeReceiverState::CANCELED || new_state == ExchangeReceiverState::CLOSED); |
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.
please use RUNTIME_ASSERT
.
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.
updated
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.
experimental , we can updated in future
Signed-off-by: bestwoody <[email protected]>
Signed-off-by: bestwoody <[email protected]>
/merge |
@bestwoody: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
@bestwoody: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/rebuild |
1 similar comment
/rebuild |
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.
/LGTM
/merge |
@fzhedu: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/merge |
/rebuild |
/run-all-tests |
1 similar comment
/run-all-tests |
/merge |
@bestwoody: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
In response to a cherrypick label: new pull request created: #4445. |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created: #4532. |
This reverts commit 25e2a26.
* This is an automated cherry-pick of #4441 Signed-off-by: ti-chi-bot <[email protected]> * Revert "This is an automated cherry-pick of #4441" This reverts commit 25e2a26. * cherry pick
* This is an automated cherry-pick of #4441 Signed-off-by: ti-chi-bot <[email protected]> * Revert "This is an automated cherry-pick of #4441" This reverts commit 25e2a26. * cherry pick * format * pass code stlye check Co-authored-by: bestwoody <[email protected]> Co-authored-by: bestwoody <[email protected]>
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.
Ignore this, just a mistake.
What problem does this PR solve?
Issue Number: close #4432
Problem Summary:
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note