You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am curious how to check log files in case we got an error from Github. In that case, we should have a message 'Error retrieving files from GitHub' in the logs or any other relevant debug information about the PR in question.
We use Bunyan so logs are available on the host as well as over http (with a secret). I'm sure @phillipj can provide the access key to those that wants to fiddle.
We use Bunyan so logs are available on the host as well as over http (with
a secret). I'm sure @phillipjhttps://github.com/phillipj can provide
the access key to those that wants to fiddle.
@phillipj thanks for follow up, you confirmed my initial assumption. A short timeout like you suggested would be sufficient as the first step. If necessary, more complicated setup with retry logic will need to take place.
Activity
sejoker commentedon Sep 18, 2016
I am curious how to check log files in case we got an error from Github. In that case, we should have a message 'Error retrieving files from GitHub' in the logs or any other relevant debug information about the PR in question.
mscdex commentedon Sep 18, 2016
Your guess is as good as mine. I've never tried to run my own instance of the bot before.
jbergstroem commentedon Sep 18, 2016
We use Bunyan so logs are available on the host as well as over http (with a secret). I'm sure @phillipj can provide the access key to those that wants to fiddle.
phillipj commentedon Sep 18, 2016
Absolutely! Just ping me on IRC and I'll give you the URL
On Sunday, 18 September 2016, Johan Bergström notifications@github.com
wrote:
phillipj commentedon Sep 19, 2016
Had a look in the logs and found this:
I assume there was some inconsistencies in GitHub's side which caused this error, while trying to retrieve the files related to the mentioned PR :/
Maybe the bot should wait a couple of seconds before doing its thing, as it's not important that these labels gets added instantaneously.
sejoker commentedon Sep 19, 2016
@phillipj thanks for follow up, you confirmed my initial assumption. A short timeout like you suggested would be sufficient as the first step. If necessary, more complicated setup with retry logic will need to take place.
sejoker commentedon Sep 19, 2016
I could prepare a PR if we agree on the possible fix.
phillipj commentedon Sep 19, 2016
@sejoker a PR would be great 👍
labels: defer resolving labels
sejoker commentedon Sep 19, 2016
@phillipj your feedback on #81 will be valuable.
labels: defer resolving labels
labels: defer resolving labels (#81)
phillipj commentedon Sep 21, 2016
FYI now that @sejoker PR is merged, the bot will wait for 2 seconds before resolving labels
Remove waiting for 2 seconds before resolving labels
Remove waiting for 2 seconds before resolving labels