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

Stalebot is being overly aggressive #2797

Closed
shoyer opened this issue Mar 3, 2019 · 7 comments
Closed

Stalebot is being overly aggressive #2797

shoyer opened this issue Mar 3, 2019 · 7 comments
Labels

Comments

@shoyer
Copy link
Member

shoyer commented Mar 3, 2019

E.g., see #1151 where stalebot closed an issue even after another comment.

Is this something we need to reconfigure or just a bug?

cc @pydata/xarray

@max-sixty
Copy link
Collaborator

I'll look into it now

@max-sixty
Copy link
Collaborator

It looks like it's a (seemingly uncommon) bug.
Given the bug, someone needs to remove the label, rather than only comment on the issue

In the meantime, we can:

  • Do nothing
  • Change the message to request removing the label
  • Disable the bot until this is resolved

Thoughts?

@max-sixty
Copy link
Collaborator

While we're here - any other feedback / suggested config changes?

We're down from ~530 to ~400 issues, and inspired a couple PRs along the way. There is some cost in swatting the marked issues though.
We were planning to move the time-to-stale to one year, from two.

@max-sixty
Copy link
Collaborator

I haven't seen this reoccur. Limited sample (though a handful of true negatives)

@stale
Copy link

stale bot commented Jun 3, 2021

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

@stale stale bot added the stale label Jun 3, 2021
@shoyer
Copy link
Member Author

shoyer commented Jun 3, 2021

Thank you, slate-bot! I think we can let this one expire now 🤣

@shoyer shoyer closed this as completed Jun 3, 2021
@max-sixty
Copy link
Collaborator

lol. I just re-logged-in a couple of days ago, since it seemed to have slept on us. Maybe the personal affront brought it back.

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

No branches or pull requests

2 participants