Continue to next packet if received broken packet #1260
Merged
Conversation
This file contains 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
Broken packet should be ignored and continue to next packet. This goroutine should not exit until close.
FedorLap2006
added
fix
|
Thanks for the contribution! |
LWCoder
pushed a commit
to AtTheTavern/discordgo
that referenced
this pull request
Apr 11, 2023
Broken packet should be ignored and continue to next packet. This goroutine should not exit until close.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Same as #1230 .
Sorry, I made a mistake and closed it.
#1166 has avoid panic but cause a silent fail.
This fixes it.
Broken packet should be ignored and continue to next packet.
This goroutine should not exit until close.