Skip to content
This repository has been archived by the owner on May 20, 2023. It is now read-only.

probot marked the issue as stale but didn't comment on it #10

Closed
rafaelfranca opened this issue Mar 27, 2017 · 3 comments
Closed

probot marked the issue as stale but didn't comment on it #10

rafaelfranca opened this issue Mar 27, 2017 · 3 comments

Comments

@rafaelfranca
Copy link
Contributor

Here is one example were the comment was not made: rails/rails#26813 (comment)

Here is one example were the comment was made:
rails/rails#25774 (comment)

Maybe the app is hitting the rate limit?

@bkeepers
Copy link
Contributor

It looks like it started hitting abuse rate limits, which I'm guessing happened between adding the label and posting the comment:

 {Error: {
   "documentation_url": "https://developer.github.com/v3/#abuse-rate-limits",
   "message": "You have triggered an abuse detection mechanism. Please wait a few minutes before you try again."
 }}

There should probably be some throttling for when an integration is first installed.

@bkeepers
Copy link
Contributor

@rafaelfranca also, I'm excited to see that Rails is using this. I'd love to hear any and all feedback.

@rafaelfranca
Copy link
Contributor Author

Yeah, a throttling should fix the problem. So far it is working really well. I'm happy to retire my manual script 😄

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

No branches or pull requests

2 participants