Live data from Hacker News

It looks like the status/need-triage label was removed

github.com

41–50 of 87 posts

Re: It looks like the status/need-triage label was removed

#41

It's easy to miss, but in the middle of the page: > 4609 remaining items Seems gemini-cli and gemini-cli didn't understand who themselves were, so they though someone else added/removed the label, which it tried to correct, which the other then tried to correct, which the other... Considering that that repository has what seems like ~10 longer term contributors, who probably get email notifications, together with a b…

> Considering that that repository has what seems like ~10 longer term contributors, who probably get email notifications, together with a bunch of other people who get notifications about it, wonder how many emails were sent out because of this? If we just assume ten people get the emails, it's already 46K emails going out in under 24 hours... Unless GitHub are idiots they batch email updates to mitigate this

[deleted]

Re: It looks like the status/need-triage label was removed

#42
post #34

Earlier quoted context omitted.

nobody who actually uses salesforce for daily work chose it. it's sold directly to CIO/CTOs as a one-stop shop for CRM, ticketing, reports and biz dev, who may occasionally use it for reporting (but more often get their staff to provide the reports directly to them). everybody stuck having to use it to actually track work just has to suffer with it.

Or in my case, it was sold directly to the CMO, and as the CTO I was stuck with it!

you won't get off that easily in the eyes of your subordinates :) but to be fair, i should have said CxOs. CEOs fall for this dogshit too.

Re: It looks like the status/need-triage label was removed

#43
post #24

It's easy to miss, but in the middle of the page: > 4609 remaining items Seems gemini-cli and gemini-cli didn't understand who themselves were, so they though someone else added/removed the label, which it tried to correct, which the other then tried to correct, which the other... Considering that that repository has what seems like ~10 longer term contributors, who probably get email notifications, together with a b…

“Everyone, just STOP PRESSING REPLY-ALL.” It’s not just bots that fall into this trap.

Unsubscribe.

Re: It looks like the status/need-triage label was removed

#44
post #40
post #15

Heh. This reminds me of the time when our newly hired "Salesforce Expert" improved our support queue: Every time Support received a new email, a ticket in Salesforce would be created and assigned to Support Every time Support was assigned a new ticket, Salesforce would send a notification email The worst part is he wouldn't admit to the mistake and it took us forever to find where he buried the rule.

Maybe 20 years ago... As a student, the school had an email server that allowed rules to be set. You could set an email to be sent as a result of another email. IT were not stupid though, and set a series of rules: 1. You cannot have a rule trigger to email yourself. 2. You cannot reply to an email triggered by a rule. 3. You have ~50MB max of emails (which was a lot at the time). Playing around one lunch, my friend…

Glad I wasn't the only person who did this.

Re: It looks like the status/need-triage label was removed

#45
post #31

It's easy to miss, but in the middle of the page: > 4609 remaining items Seems gemini-cli and gemini-cli didn't understand who themselves were, so they though someone else added/removed the label, which it tried to correct, which the other then tried to correct, which the other... Considering that that repository has what seems like ~10 longer term contributors, who probably get email notifications, together with a b…

> did someone pay for all of these inference calls here? Considering that these responses are all the exact same two replies in wording, and that this is a task which could be easily automated without AI, I seriously doubt that it's going to be caused by actual inference.

I didn't think that the GitHub responses themselves were LLM generated, but considering the name, I assumed that even incoming responses might be passed through something that ends up doing inference calls, but that very well might not be the case here at all. Doesn't seem like something that'd be even hard to do without inference, so you might be right.

Re: It looks like the status/need-triage label was removed

#47
post #40
post #15

Heh. This reminds me of the time when our newly hired "Salesforce Expert" improved our support queue: Every time Support received a new email, a ticket in Salesforce would be created and assigned to Support Every time Support was assigned a new ticket, Salesforce would send a notification email The worst part is he wouldn't admit to the mistake and it took us forever to find where he buried the rule.

Maybe 20 years ago... As a student, the school had an email server that allowed rules to be set. You could set an email to be sent as a result of another email. IT were not stupid though, and set a series of rules: 1. You cannot have a rule trigger to email yourself. 2. You cannot reply to an email triggered by a rule. 3. You have ~50MB max of emails (which was a lot at the time). Playing around one lunch, my friend…

You were not the root cause of that outage.

> IT were not stupid

Everything else you described points to them being blundering morons. From an email forwarder that didn’t build loop detection into its header prepending, fucking up a restore, and then malware’ing the student that exposed them into kafkaesque technology remand, all I’m taking away here is third-degree weaponised incompetence

Re: It looks like the status/need-triage label was removed

#50

A similar issue made HN last week, same repo, where an AI bot was having the same kind of argument with itself over and over on an issue. Someone mentioned: This sort of thing is why RAM is 800 bucks now.

This is the thread:

https://news.ycombinator.com/item?id=46636291

Post reply on HN