Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

21–30 of 87 posts

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

#21

Post by philipwhiuk »

embedding-shape wrote: post #4

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

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

#22

Post by bedatadriven »

PyWoody wrote: 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.

I can remember something like this a few years ago when a customer emailed our helpdesk with their own internal IT support desk in copy. Our helpdesk at the time sent a complete new email acknowledging the request, which the customer's desk ALSO acknowledged in a new thread...

I think it took us a good hour and a few hundred tickets to get the helpdesks to stop fighting with each other!

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

#23

Post by m0llusk »

embedding-shape wrote: post #4

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…

Some are saying there is no more room for junior employees in all of this, but it seems like these LLM spasms generate lots of disruption that would be at appropriate levels of complexity and priority for juniors to be handling.

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

#24

Post by sneak »

embedding-shape wrote: post #4

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.

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

#25

Post by embedding-shape »

pousada wrote: post #20
PyWoody wrote: 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.

I only used salesforce once (was “forced” to use it haha) and it was mind boggling how anyone would ever want to use it or even become an expert in using it. I’d rather track everything in a giant excel tyvm

> it was mind boggling how anyone would ever want to use it or even become an expert in using it.

As in a lot of cases, the answer is money. If you have expertise in Salesforce, you can get paid a lot, especially if the company you contract/freelance for is in an "emergency" which, because they use Salesforce, they'll eventually be. As long as you get the foot in the door, you'll have a steady stream of easy money. It fucking sucks though, the entire ecosystem, not for the weak of heart.

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

#26

Post by embedding-shape »

philipwhiuk wrote: post #21
embedding-shape wrote: post #4

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

Yeah, they probably do batching, but not by "day" intervals exactly, probably minute if not second. Still end up with a whole lot of emails, probably 50K+, within some hours.

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

#27

Post by embedding-shape »

sneak wrote: post #24
embedding-shape wrote: post #4

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.

The linked issue literally only have one bot falling into that trap...

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

#28

Post by a-dub »

in the old days one would add and check for a loop detection token when loops like this could be driven by external systems... i wonder if today it would be as simple as adding "ensure you don't get stuck in any loops" to a prompt.

fwiw. doesn't look like gemini at all, the responses are perfectly canned... maybe just good old fashioned ci rules.

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

#29

Post by trgn »

PyWoody wrote: 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.

> and it took us forever to find where he buried the rule.

Salesforce is such an ugly beast

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

#30

Post by GuinansEyebrows »

pousada wrote: post #20
PyWoody wrote: 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.

I only used salesforce once (was “forced” to use it haha) and it was mind boggling how anyone would ever want to use it or even become an expert in using it. I’d rather track everything in a giant excel tyvm

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.
Post reply on HN