Closed jamesjoshuahill closed 5 years ago
:white_check_mark: Hey jamesjoshuahill! The commit authors and yourself have already signed the CLA.
Hey @jamesjoshuahill and @MModhaPivotal, really appreciate the PR and nice work on finding this bug (its tricky) 👯♂️
After looking at this a bit, we're think we found a hybrid solution (that we pushed today) that maintains the goroutine while solving the issue of more writes than reads happening to the publicKeyChannel
. We used your tests too, they were very helpful!
We wanted to keep the goroutine because switching from a non-blocking call to a blocking call could be a big change, and we wanted to keep the changes to a minimum while still solving the bug. We're open to discussion.
https://github.com/cloudfoundry/socks5-proxy/commit/7ade90b228c8472a45c189e77f78497b93bbaeaa
cc: @zachgersh
Hi @Polar-Beard and @zachgersh
Thank you for reviewing our PR 😄
We didn't consider the impact of removing the go routine on consumers. Thank you for addressing this in the hybrid solution.
Also, thank you very much for:
github.com/cloudfoundry/bosh-utils
: https://github.com/cloudfoundry/bosh-utils/pull/67.💯Maximum community points!
Many thanks Josh
cc: @cloudfoundry/bosh-backup-and-restore-team
This caused an issue in the BBR CLI, see https://github.com/cloudfoundry-incubator/bosh-backup-and-restore/issues/25. When the wrong private key is used in
BOSH_ALL_PROXY
the CLI hangs indefinitely.This is a non-breaking change.
Josh and @MModhaPivotal