-
Notifications
You must be signed in to change notification settings - Fork 83
fix: catch discard error and return #204
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
base: main
Are you sure you want to change the base?
Conversation
6976588 to
be12196
Compare
|
Sorry for the late reply. I've updated GitHub Actions. Can you rebase this PR against main? |
be12196 to
fe96bdd
Compare
|
done thanks @kzys |
|
Did you confirm this fixed the issue? Looking through the bufio implementation of |
fe96bdd to
e3b5a07
Compare
|
you are right I create new pr will fix. @dmcgowan |
2f33066 to
72984df
Compare
|
Catching any error on discard makes sense and exiting. If the discard did not succeed then the connection must be ended as it is no longer in a processable state. |
72984df to
c12e5ff
Compare
|
done thanks @dmcgowan |
Signed-off-by: ningmingxiao <ning.mingxiao@zte.com.cn>
c12e5ff to
847da32
Compare
to fix containerd/containerd#12669 @fuweid @dmcgowan
recvErr will not receive an error when discard failed and go func will not return.
or we can catch discard error and return