tag:help.lighthouseapp.com,2008-09-20:/discussions/problems/682-github-integrationLighthouse: Discussion 2011-04-09T00:34:22Ztag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-17T11:28:09Z2009-04-17T11:28:09Zgithub integration<div><p>In your github account, can you check to make sure the hook is
set to active? there is a check mark next to where you enter your
Lighthouse key.</p></div>Will Duncantag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-17T11:45:10Z2009-04-17T11:45:10Zgithub integration<div><p>Somehow, this is working this morning, i'm not sure what was up
prior to this morning. But to answer your question, i had it active
the whole time.<br></p>
<p>Thanks!</p></div>Gennady Borukhovichtag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-17T11:47:34Z2009-04-17T11:47:34Zgithub integration<div><p>That's really strange, but I'm glad it's working. If it happens
again, please let us know...</p></div>Will Duncantag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-18T02:24:01Z2009-04-18T02:24:01Zgithub integration<div><p>It takes a while for changesets to register in Lighthouse, it is
not automatic, even if they are shown in Github at the time.</p></div>rey.writetag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-18T11:55:16Z2009-04-18T11:55:16Zgithub integration<div><p>Yes, there is a tiny delay between commits are pushed to GitHub
and tickets are updated on LightHouse.</p>
<p>However there seem also to be a delay between marking ticket as
resolved (by GitHub commit) and ticket disappearing from ticket
list of current milestone.</p></div>michal.szajbetag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-19T18:41:46Z2009-04-19T18:41:46Zgithub integration<div><p>Changesets showing in the Lighthouse timeline really depend on
when Github sends them. The ticket updates are thrown into our job
queue and can take little longer (usually much less than a minute).
What kinds of delays are you seeing?</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-19T18:50:39Z2009-04-19T18:50:39Zgithub integration<div><p>It usually takes anywhere from 30 secs to 1 minute for them to
register, which is to be expected, since the change actually has to
be pushed to github, registered on github, and then sent to
lighthouse and show up there (at least I'm guessing that's how the
workflow/api works). It's somewhat expected.</p></div>rey.writetag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-19T23:44:11Z2009-04-19T23:44:11Zgithub integration<div><p>I am aware that delays between github and lighthouse are normal
thing.<br>
However I am talking about following situation:</p>
<p>I commit a change to github, ticket gets resolved at Lighthouse
(I see<br>
it's resolved on ticket's page: projects/X/tickets/Y). I go to
current milestone's tickets (projects/X/milestones/current)<br>
and I see that ticket there still marked as new. Seems like no<br>
automatic cache expiration after ticket update by github. The
ticket disappears from current milestone's tickets list only
after<br>
I manually update another ticket. Like this action actually
expires<br>
cache.</p>
<p>Hope that's more clear now :)</p></div>michal.szajbetag:help.lighthouseapp.com,2008-09-20:Comment/1338912009-04-20T16:49:16Z2009-04-20T16:49:16Zgithub integration<div><p>Thanks michal, that's clearly an expiration bug. I'll get that
fixed today.</p></div>Rick