-
Notifications
You must be signed in to change notification settings - Fork 300
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: client panic #719
fix: client panic #719
Conversation
Signed-off-by: Jim Ma <[email protected]>
Signed-off-by: Jim Ma <[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.
LGTM
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
Signed-off-by: Jim Ma <[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.
LGTM
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
* fix: client panic Signed-off-by: Jim Ma <[email protected]> * chore: update ginkgo version Signed-off-by: Jim Ma <[email protected]> * chore: avoid send failed piece hang Signed-off-by: Jim Ma <[email protected]>
Signed-off-by: Jim Ma [email protected]
Description
When close
pt.failedPieceCh
, if there is some goroutines are downloading pieces, then sends failed pieces, the client panics(recover by client).Related Issue
Motivation and Context
Screenshots (if appropriate):
Types of changes
Checklist: