#StaleBot
Totally normal #Python upstream attitude:
1. Ignore a reply on a bug report for 3+ years.
2. Install a #StaleBot in the middle of the night.
3. 7 minutes after the bug is marked stale, claim that you "never heard back on this" and that "the issue was somewhere downstream", without even checking another linked issue.
https://github.com/matplotlib/matplotlib/issues/23384#issuecomment-3652630086
@grishka @Antacon @sjvn Personally I also keep issues open but will give them a specific tag like waiting for reply as a placeholder.
Yaiy, my #Signal desktop client now says: "Unlinked: Click to relink Signal Desktop to your mobile device to continue messaging."
But I can't, because my old phone still has the issue of a broken #sqlite database after a battery failure while messaging. And the ticket for that was closed via a #StaleBot, even though I bumped that ticket... https://github.com/signalapp/Signal-Android/issues/13814
Is the only way to use Signal again to install it without migration on my new phone?
@pancake Relative.
- I think in that case there's rather a systemic problem of underresourced #FLOSS projects: More funding and personnel would greatly help in said effort.
The only thing #StaleBot generates are #duplicates due to new tickets being opened with the exact same problem…
- It's almost as garbage as using #discord for #documentation and #support when #MkDocs-Material on #GitHubPages would've done a better job and not create yet another #InformationBlackhole!
I don't deny the issue at hand; I just think that such a massive pile needs to be combed through better by using tags and prioritization. Even if that means one has split the backlog into half a dozen different baskets that read "feedback", "suggestion", "bug", "security", "ui/ux", "building", "l18n/i18n", "accessibility", "reproduceability", etc...
@404mediaco #stalebot comes for open access to information! (this has to be illegal, but why would they care)
Смерть конфигурации stale-ботов, которая автоматом закрывает тикеты! Это отвратительно.
I opened a bug ticket on the Homebrew issue tracker. It is a legitimate bug, with a reproducer provided, maintainers agreed.
I managed to keep it open for six weeks by commenting every time #stalebot barged in (just posting a link to Drew Devault's article), before someone showed up to condescend and strawman me, saying I must have bad intentions towards Homebrew if I don't like stalebot.
Then the ticket was summarily closed and locked as unproductive (because I dared criticize their stale policy), and as "hard to debug" (despite being 100% reproducible with the code I provided), proving my point.
Would not recommend contributing to that project. They clearly do not value having a community.
Ah yes, the refined way of running an OSS repo. You configure dependabot to keep you up to date, ignore it's PRs and have the stalebot close the PRs 90 days later.
Perfectly in balance, as nature intended.
This revelation brought to you by trying to compile #Ceph and failing because they pin deps from 2022 that won't compile anymore with modern versions of Python, and unsurprisingly never shipped wheels for versions of python that were not really yet mainstream at the time. (py311 was already out, but no grpcio==1.46.5 wheel for it.)
I guess I'll try bumping the dep pins locally and hoping for the best.
@truh @thcrt @MastodonEngineering @Gargron I think #StaleBot should not be used to closed issues!
- Rather use it to mark posts waiting for a reply from the original poster needed...
I do not know why the Home Assistant developers foster such a hostile environment, and I really hope it doesn't push the whole ecosystem backwards again. (This new legal entity seems like a very bad sign to me, but I've had entirely too much experience with "corporate" open source.)
The "Cool Kids" clique has managed to negatively impact everything. Did you get kicked out of HACS by a malicious request? Too bad! Found a simple easy-to-reproduce bug? File an excellent report, and sit back until stalebot closes it. Oh but you have a patch? It got rejected! Don't worry though, because there is a decent chance a Cool Kid will copy it and submit it as their own. Did you find a security issue? Oh no! File it quick to protect everyone! Too bad they will tell you it is invalid, and then later they will post-date the notification so they can give tons of public credit to a Cool Kid instead.
And these are just incidents that I am finding by accident as I try to use and contribute to this fucking mess. Almost every time I have to deal with the core ecosystem it turns out that the bug is old. Usually someone else already tried and got shit on (or ignored until the robot says "fuck off you don't matter".) Sometimes I get unlucky and it is my turn to get the stinky end of the stick. Usually I don't bother anymore.
This is not about scale. This isn't even about #stalebot, although of course stalebot helps gatekeep by ignoring the Cool Kids. This isn't about misfiled tech support "bugs", or about improper disclosure. This isn't about "that mean person told me my code sucked." This is purely about the "Us vs Them" gatekeeping bullshit.
I originally wrote this out with a bunch of examples, but every third word being a link to a bug or blog (or both) took something away from it.
#homeassistant #hassio #hacs #homeautomation #selfhosting #selfhost