-
Notifications
You must be signed in to change notification settings - Fork 50
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
Iv 2077 proxy #16
Iv 2077 proxy #16
Conversation
Panics in websocket pinger should probably not ever be fatal
Code Coverage is 57.7%, details at https://s3.amazonaws.com/rs-code-coverage/wstunnel/2015-06-19_60_Coverage-57.7.txt (sometimes the URL can take a few minutes to be available) |
Code Coverage is 56.8%, details at https://s3.amazonaws.com/rs-code-coverage/wstunnel/2015-06-23_62_Coverage-56.8.txt (sometimes the URL can take a few minutes to be available) |
7bbbae1
to
3bfa01c
Compare
Code Coverage is 57.6%, details at https://s3.amazonaws.com/rs-code-coverage/wstunnel/2015-06-23_64_Coverage-57.6.txt (sometimes the URL can take a few minutes to be available) |
t.exitChan = make(chan struct{}, 1) | ||
waitForConn := make(chan struct{}, 1) |
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.
I don't understand what this is doing.
@tve, add HTTPS proxy support to tunnel.
Spec changes are not as extensive as they seem. Combined internal tests into basic tests as they were the same tests with a couple things tweaked. Did this by putting them into a function -- none of the content of the tests themselves was changed. The function is then run in different gomega Contexts with appropriate setup for each.