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
It looks like the status/need-triage label was removed
41–50 of 87 posts
Re: It looks like the status/need-triage label was removed
#42Earlier 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!
Re: It looks like the status/need-triage label was removed
#43It'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.
Re: It looks like the status/need-triage label was removed
#44Heh. 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…
Re: It looks like the status/need-triage label was removed
#45It'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.
Re: It looks like the status/need-triage label was removed
#46Normally I would complain about people spamming in GitHub issues but I don't think it will matter this time
Re: It looks like the status/need-triage label was removed
#47Heh. 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…
> 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
#48gemini-cli did much more work in this PR then the author himself.
Re: It looks like the status/need-triage label was removed
#49Finally an example of AI doing something useful. Imagine having to add and remove all those tags 4500+ times by hand!
Re: It looks like the status/need-triage label was removed
#50A 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.