#stalebot — Public Fediverse posts

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

#Matplotlib

#StaleBot, ale zamiast odgrażać się, że odrzuci przesłaną łatkę, to grozi, że ją włączy do kod. Wszak skoro nikt nie ma uwag, to musi być dobra, nie?!

#GitHub

#StaleBot, except instead of threatening the contributor to close the PR, it threatens the maintainers that it will merge it. Obviously, since there are no remarks, it must be good!

#GitHub

@404mediaco #stalebot comes for open access to information! (this has to be illegal, but why would they care)

Смерть конфигурации stale-ботов, которая автоматом закрывает тикеты! Это отвратительно.

https://nostalebots.xyz

#NoStaleBots #StaleBot

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.

why is #stalebot

do better, @homebrew

#StaleBot znów przynosi szkody. Tym razem opiekun projektu był tak pochłonięty konfiguracją bota, że zignorował błąd składni, zgłoszony przez CI, wrzucił spieprzoną łatkę do projektu, a następnie wydał totalnie nową, totalnie spieprzoną wersję.

https://github.com/wolph/python-progressbar/pull/298

#Gentoo #Python

#StaleBot is at it again. This time, the project maintainer was so busy configuring their stale bot that they've entirely missed the syntax error reported by CI, merged a broken pull request and then made a completely broken release.

https://github.com/wolph/python-progressbar/pull/298

#Gentoo #Python #WTF

Motion to ban #StaleBot

Właśnie odkryłem https://nostalebots.xyz/ i zgłosiłem dwie organizacje. Zróbmy listę wstydu dla projektów, które nie szanują użytkownika i wysyłają #StaleBot na zgłoszenia błędów.

Jeżeli ktoś chce oznaczyć moje zgłoszenie jako nieaktualne, niech z łaski swojej pofatyguje się zrobić to osobiście, tak jak ja pofatygowałem się, by problem zgłosić osobiście. Albo jeszcze lepiej, niech użyje skryptu do reprodukcji, o ile udało mi się taki przygotować.

#GitHub #WolneOprogramowanie

I've just learned that there's https://nostalebots.xyz/ and I've just reported two organizations. Let's make a shame list of projects that disrespect their users, and send #StaleBot after their bug reports.

If you want to mark my bug report stale, at least bother doing it personally, just like I bothered filing it. Or ideally, run my reproducer if I managed to provide one.

#GitHub #OpenSource

@dcz @malte I get so upset when I see issues closed automatically after inactivity, it makes my heart sink. At least it looks like they stopped doing this 10 months ago in this project, but without reopening the auto-closed issues… https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/?sort=created_date&state=closed&label_name%5B%5D=auto-closed&first_page_size=20
#stalebot #NetworkManager #FreeDesktop

#Stalebot ist auch nur #QuietQuitting mit besserer Ausrede -.-