Skip to content
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

Unit/Integration tests fail sometimes due to netty.io responding with a 522. #8

Closed
zerkz opened this issue Jul 15, 2015 · 4 comments
Closed

Comments

@zerkz
Copy link

zerkz commented Jul 15, 2015

Noticed this pretty often. Are we accidently ddosing the site? Cloudflare seems to be up often.

Either way, we should add a check to pass the test if it 522's, so that we don't have to skip tests for installs often.

@ganskef
Copy link
Owner

ganskef commented Jul 15, 2015

Which test? It should be fixed with commit c907a0f.

I think, you have to merge upstream tracking, like described here:

  1. https://help.github.com/articles/configuring-a-remote-for-a-fork/
  2. https://help.github.com/articles/syncing-a-fork/

If you've fetched my repo, you could try git cherry-pick c907a0f. (But, I'm a Git newbie)

@ganskef
Copy link
Owner

ganskef commented Jul 15, 2015

I've cherry picked it into the netty_proxy_client branch, too.
I'll investigate #4 to describe the intend of the branch more clearly.

@zerkz
Copy link
Author

zerkz commented Jul 15, 2015

Cool, does look like it was fixed in that comment. thanks!

@ganskef
Copy link
Owner

ganskef commented Jul 15, 2015

Ok, I'm going to close this.

@ganskef ganskef closed this as completed Jul 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants