Comment by halpow
Comment by halpow 7 days ago
Don't forget all major OSS repositories using a stale bot to close any issue regardless of how many people reported it or how serious it is. Close and lock at times. Yikes.
Comment by halpow 7 days ago
Don't forget all major OSS repositories using a stale bot to close any issue regardless of how many people reported it or how serious it is. Close and lock at times. Yikes.
I think that once a bug has been verified and keeps getting likes, it should not be closed.
If the user never responded to further questions, then absolutely.
What I see however is that maintainers themselves fight the bot removing the label and reopening issues. Over and over. Until they miss the notification.
> The stale bot approach does help in cases where a bug does not have merit. For example, not that long ago, a user opened a bug asking us to rename the ZFS Event Daemon so a text editor could adopt the daemon’s name. The consensus among contributors on the discussion is that we will not do it, but no one has volunteered to be the one to close the bug. The stale bot will be closing that one for us.
That doesn't sound like an even remotely ideal way to handle that. Don't just needlessly string the original reporter along until some arbitrary time limit expires.
I stopped reporting bugs when I see the repo is using stale bot. One thing is to be ignored for a while, because maintainers are busy. Another one is to be told "we ignored you long enough, it is not an issue".
Yes it still is. I made a reproducible example, try it out.
Yep, stale bot got me to stop reporting bugs to Kubernetes, I spend time to gather details for an useful and it just gets closed without any human interaction. That's super disrespectful.
I have seen OpenZFS adopt one, but whenever I have seen a bug that has merit closed by the stale bot, it is reopened by a contributor and a not-stale flag is added to prevent it from being automatically closed again. Note that I am a contributor, but I am not one of the ones who is reopening bugs and marking them as not stale. The few times I saw such a bug and would have done it, someone else beat me to it.
The stale bot approach does help in cases where a bug does not have merit. For example, not that long ago, a user opened a bug asking us to rename the ZFS Event Daemon so a text editor could adopt the daemon’s name. The consensus among contributors on the discussion is that we will not do it, but no one has volunteered to be the one to close the bug. The stale bot will be closing that one for us.