fix: CopyRemotePassThru blocked on writing to error channel #56
+49
−8
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.
While trying to download a file from an remote endpoint, I gave the wrong flags to os.Openfile(dstFileName, os.O_CREATE, 0644), thus creating a lock in my code.
Digging in the code, I saw that the scp client was blocking on a write to errCh in CopyFromRemotePassThru. Adding the wg.Done() unblocked the situation.
Maybe related to #54 and #55
Also, all errors seem to be written twice on errCh as the error is persisted as a variable.