prevents a goroutine from being leaked if a timeout occurs when calling forceCloseConnection #2854
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.
Summary
Fixes potential edge case which could result in a goroutine leak, applies general best practice for working with channels.
A goroutine leak could occur in the following edge case scenario:
In the case that the
case
in https://github.com/aws/amazon-ecs-agent/blob/master/agent/wsclient/client.go#L274-L285 executes first, the function will return and the anonymous goroutine in https://github.com/aws/amazon-ecs-agent/blob/master/agent/wsclient/client.go#L269 would continue to be blocked, causing a goroutine leak. Using a buffered channel prevents this issue.Implementation details
Made an unbuffered channel into a buffered channel
Testing
New tests cover the changes: no
Description for the changelog
bugfix - fix potential goroutine leak when closing websocket connections
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.