DisMar 20, 2023

If your #github project uses #stalebot you are being actively hostile to your community and should stop it.

I'm looking at you, #esphome, and the 4 (at least!) identical bugs indicating problems with esp_touch that were all closed by stalebot. Some of them were reproduced and started discussion and debugging before being closed.

Auto-closing is for #support requests, not #bug reports. Bugs don't magically disappear just because you ignore them.

Show threadMiroslav SuchýMar 27, 2023
@dis when you look at Issues as a list of known bugs in a project, then you are right. But if you would see it as a queue of issues to be fixed then having it open for 2+ years is a false hope to a community that the issue gets fixed. Nope. It rarely happens for old issues. I agree that the default value for daysUntilStale is too low. But 365+ days is OK for me.
Show threadAntonin DelpeuchMar 27, 2023
@mirek @dis in #OpenRefine, I am working on issues that are 10+ years old. I am glad they have not been closed automatically because they are about (I think) great improvements that are still totally relevant today. Example: https://github.com/OpenRefine/OpenRefine/issues/87
Long running processes should serialize intermediate results · Issue #87 · OpenRefine/OpenRefine

Original author: iainsproat (June 23, 2010 15:58:35) For a long running process in mid-calculation, long running processes should serialize their intermediate results. Later recovery could be suppo...

GitHub
Show threadDis

@pintoch @mirek 10 years is a while. Recently I snickered when an old project I contributed to finally got around to triaging a breaking bug I reported in 2011.

Like, I love the dedication but this is a #puppet accessory app. Who still uses #puppet?? Its been a full dot-com bubble since then! (And no, I am not going to reproduce that RHEL4 bug for you here in 2023. My career is intentionally at a point where I never have to reproduce anything in RHEL ever again.)

Mar 27, 2023 at 9:28pmWeb
Show threadAntonin DelpeuchMar 27, 2023
@dis @mirek but in big projects that's really not that uncommon! For instance this issue about handling of non-breaking spaces in #Firefox. Opened 17 years ago, closed 10 months ago by @pmorinerie. It's worth it! https://bugzilla.mozilla.org/show_bug.cgi?id=359303
359303 - Non-breaking spaces (nbsp) not copied as such

RESOLVED (kemenaran) in Core - DOM: Serializers. Last updated 2022-07-22.