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

GitHub webhook sometimes gets an HTTP 504 Gateway Timeout from CLAHub #38

Open
jasonm opened this issue Feb 18, 2013 · 4 comments
Open

Comments

@jasonm
Copy link
Member

jasonm commented Feb 18, 2013

I'm trying to verify the CLAHub setup for Molajo/Filesystem - specifically, Molajo/Filesystem#2. That project is using TravisCI, so #27 still applies here and we'll currently only see one status indicator at a time (Travis or CLAHub) for a given pull.

That said, I can see via API access that CLAHub never correctly set a status on Molajo/Filesystem@3636c37 for Molajo/Filesystem#2.

In fact, when GitHub sent a Webhook to CLAHub, CLAHub responded with a 504 Gateway Timeout:

irb(main):008:0> pp g.repos.hooks.find('Molajo', 'Filesystem', a.github_repo_hook_id)
{"url"=>"https://api.github.com/repos/Molajo/Filesystem/hooks/ID_REDACTED",
 "test_url"=>
  "https://api.github.com/repos/Molajo/Filesystem/hooks/ID_REDACTED/test",
 "id"=>ID_REDACTED,
 "name"=>"web",
 "active"=>true,
 "events"=>["push"],
 "config"=>{"url"=>"http://www.clahub.com/repo_hook"},
 "last_response"=>{"code"=>504, "status"=>"timeout", "message"=>""},
 "updated_at"=>"2013-02-17T08:47:45Z",
 "created_at"=>"2013-02-06T06:33:13Z"}

It could have been that CLAHub was running on a single Heroku Dyno and did not spin up in time, or that the processing simply took too long.

Ideally GitHub webhooks would retry if given a non-2xx response. Absent that, we should ensure CLAHub always has at least 1 dyno. Since Heroku also imposes a 30-second limit on response time, we likely also want to background all webhook responses, similar to #1.

@jasonm
Copy link
Member Author

jasonm commented Feb 18, 2013

I've inquired with GitHub support about webhook retries.

@jasonm
Copy link
Member Author

jasonm commented Feb 18, 2013

@AmyStephen if you get a moment, could you do me a favor and try going to Molajo/Filesystem settings > Service Hooks > WebHook URLs and clicking "Test Hook"?

Service Hooks

And then see if Molajo/Filesystem#2 gets a CLAHub status? It might not right away (because of TravisCI maybe overwriting it), but I'm curious for you to try it. Thanks!

@AmyStephen
Copy link

Doesn't appear to be updating.

If it helps for testing, I can make you an Admin of the repository.

@damtur
Copy link

damtur commented Nov 11, 2015

I've inquired with GitHub support about webhook retries.

@jasonm Can you please add a link to that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants