@mattst88 #stalebot is still up there though, maybe not on top but up there somewhere 😸

Unpopular opinion:

The #stalebot on #nixpkgs should close PRs after some months of inacitivity.

I mean... there are PRs open that conflict and had no interaction since 2021... why not close them?

#Vote time! Should I spend the day continuing to identify and fix bugs (and non-removable #spyware #analytics) in @grafana #loki #helm chart, or should I fix the #prusa again?

The first is likely to make me angry on the internet, but it will materially advance the new #homelab. Existing history says they won't accept any outside contributions though. (The first bug I need to fix is a one-line fix that the humanoid #stalebot found and rejected. And they are unlikely to accept PRs that make the spyware less .... spy-ee, which includes resisting efforts to document it.)

The second task is likely to burn my fingers and make me frustrated at the world in general. I'm pretty sure I just need to redo the nozzle and a Z alignment. On the other hand, doing that with a #Prusa is an exercise in frustration and poor design. "Grab this hot thing without touching the wires that literally prevent you grabbing it anywhere without blocking the next step. Also those wires are broken."

@fsniper https://techhub.social/@dis/110057503427579633

At a glance this morning, it looks like my original issue has 3 duplicates currently open, plus the 4+ closed ones I counted before. None of the developers have interacted with any of the open ones I found. Just users, alone in the dark debugging and fending off stalebot (or giving up and quitting)

#esphome #bugs #bugreports #github #stalebot #aiart

I just tripped over a real-life #stalebot LARPer. A human maintainer who wandered around closing stuff because they were bored. (And yes, it was on a commercial "open source" project, so they probably got paid for it.)

"Here is a trivial fix for a stupid bug."
"Oh sorry, while it is only a 2 line patch, I can't be bothered to look. Closed for inactivity."

(Bonus: simple "enabled: true" testing would show that the chart doesn't template because of this bug. As trivial to replicate as it is to fix.)

This is proving to be a very annoying week.

#helm #github

My #HomeAssistant is pushing a ton of huge "danger!" warnings saying:

> To improve Bluetooth reliability and performance, we highly recommend updating esp-coffee-v4 with ESPHome 2023.6.0 or later.

You may wonder why my devices are out of date. I'm generally pretty good about updates and #BigEar uses #bluetooth a LOT.

They are out of date because I had to downgrade them. Why? **Because 2023.6.0 and later completely and totally broke bluetooth.**

Who the ~fuck~ tested this? And as a bonus, why was it not mentioned in the changelog? It is "important" enough to be pushed as an *urgent change* but nobody fucking TESTED IT first?

At least #stalebot keeps all the developers from having to see bug reports.

#snarkhome #qa

To clarify a bit, the reason I don't argue with #stalebot more than once is simple: Filing a good bug report is hard work. (I'm not referring to feature requests, although those can be hard work too.)

A project that uses #stalebot invariably accumulates tons of valid but closed bugs. A few of them will get accidentally fixed, but most remain real and get lost. (A closed bug looks fixed, so users tend to open a new one.) This feeds the "need" for stalebot because "omg too many bugs!" even though they are just noise generated by stalebot to begin with.

Back to #esphome: Why should I spend at least 30 mins searching their junk pile, plus at least an hour of gathering logs, experimenting, etc?

The humans involved will never look at it, and eventually their robotic receptionist will tell me to go away. I refuse to put more effort into this than they do.

#esphome #github #stalebot #homeassistant #bugs #bugreports #snr #qa

Today's total pile of horse dookie is courtesy frequent-flyer #ESPhome. The latest release completely broke #BLE (and by extension, my #bigear)

Weirdly, #homeassistant can still "see" the tags, with it's broken distance calculation (weighted average?) and useless "source" field.

I'd file a bug but I am not arguing with #stalebot again. (And even their humans are not great.)

#homeautomation #snarkhome #esp32 #ibeacon

This morning's wizarding is a new case for my #esphome speakers. Specifically, I love https://www.printables.com/model/363300-esphome-speaker but it doesn't fit the ESP32 boards I settled on ( https://amzn.to/3JA0lpA )

If #esphome supported #i2s on #esp8266 this wouldn't be an issue. I have plenty of esp8266 boards that are roughly the right size. Alas, filing a bug would involve another fight with #stalebot.

Instead of climbing the #barriertoentry, I fired up #Fusion360 (thanks https://usebottles.com/app/#fusion360 !) and whipped up a quick alternate box bottom.

Unfortunately, some terrible no good very bad filament from #Sunlu has managed to completely jam my extruder right below the gear, so I can't print it yet.

I am so tired of rebuilding this stupid #Prusa. The hot-end was decent before the #mmu2 disaster, but that conversion and subsequent fix-after-fix has made it sketchy at best. At least I'm getting good at teardowns. (And I'm saving for the top MK4 upgrade to get rid of the PTFE entirely.)

dependabot and stalebot do more harm than good.

Change my mind.

#dependabot #stalebot #opensource #softwaredevelopment #packaging #developerexperience #lamehashtags

@mirek You don't get hope from a 10 year old ticket. You get continuity, debugging, more information and validation. You may even get a fix.

I'm not going to contribute time (or code, or docs, or debugging effort) when the gatekeepers use #stalebot as a recording to say "We're sorry, all representatives are busy with contributors that aren't you. Please go away.<click>"

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.

Not labeling CWs as CWs when the body text is empty has been a known issue with #Mastodon for over three years: https://github.com/mastodon/mastodon/issues/6825

@ClearlyClaire opened a PR later In 2018 but no one merged it and the stupid #GitHub #StaleBot closed it as “wontfix”: https://github.com/mastodon/mastodon/pull/9046#issuecomment-546567972