[embedding-shape]

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 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...

Also, who pays for the inference of this gemini-cli? Clicking the "user" links to https://github.com/apps/gemini-cli, and it has a random GitHub user under "Developer", doesn't seem like it's a official Google project, so did someone pay for all of these inference calls here? That'd be a pretty sucky bill to pay...

[TACD]

This isn't the first time it's happened, either. It's a pretty frequently recurring issue, in fact:

https://github.com/google-gemini/gemini-cli/issues/16723

https://github.com/google-gemini/gemini-cli/issues/16725

https://github.com/google-gemini/gemini-cli/issues/16732

https://github.com/google-gemini/gemini-cli/issues/16734

[embedding-shape]

All opened the 15th of January though, same as the instance linked in the submission. Seems maybe more accurate to say "widespread issue" rather than "frequent issue", as it seems to only have happened at one occasion, but it had time to spam many issues on that day.

[hirsin]

The owner is a Google employee, but for the sake of safety it should be owned by a real Google org. I've just asked them to migrate it to their OSS org.

Unfortunately the app creation flow on GitHub makes it impossible (for now) for a normal org user to create an app for the org, so apps end up getting created on personal accounts and become load bearing. We've got a work item to make it possible to give app creation rights to your org members, I've got it high on the priority list for the next six months.

Re:payment As I understand it each org that uses the gemini cli agent puts their api key in their actions secrets, which gets picked up and used to call Google inference APIs. So the org these comments are in is paying for the inference.

[htrp]

Dear god. This reminds me of all of the things in Google that are "load bearing" and have to be owned by random gmail accounts instead of formal service accounts or org accounts.

How long has this one been on the roadmap for? (since you actually work for github)

[hirsin]

Tbc apps can be owned by orgs today, but the process is annoying - devs create the app and then transfer it to the org, and then are made managers of the app. Really high overhead.

It's part of the push we've been making over the last year or two to improve custom roles and finer-grained authorization for resources.

[oooyay]

The first event-driven agent I ever built ran into this style of bug. The bot had a name, it knew the name, but what it didn't know is that the name could show up as a user ID in various forms and then it didn't know how to recognize itself. Every view the agent has needs to be curated towards the agents understanding of itself and the world around it, you can't just spew API results at it.

[m0llusk]

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.

[esafak]

What if a junior with an LLM did this?

[DANmode]

What about an LLM with a junior?

[fragmede]

LM?

[DANmode]

The joke was that the chatbot is driving the junior developer,

not the other way around,

a nonzero amount of the time.

[sneak]

“Everyone, just STOP PRESSING REPLY-ALL.”

It’s not just bots that fall into this trap.

[embedding-shape]

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

[NitpickLawyer]

The quote is from one of the old "mail storm" stories out there. Where someone miss-configures something, someone e-mails a list, people are out of office, people reply-all, and hilarity ensues. Plenty of them posted on slashdot and the like back in the day.

[fragmede]

who ate all the bananas?

[cyberax]

Unsubscribe.

[philipwhiuk]

> 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

[embedding-shape]

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.

[eviks]

> Thank you for your understanding! × 4609

[netsharc]

Google Gemini 2028!

[Sophira]

> 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.

[magicalist]

Yeah, this looks more fun than it is because the bot is named "gemini-cli".

This is just two github actions conflicting with each other, one that auto-labels with "status/need-triage" and the other that incorrectly sees gemini-cli as lacking the permission to do that.

The fix looks like it was https://github.com/google-gemini/gemini-cli/pull/16762 because the bot adding labels wasn't passing the org-level ownership check they used at first.

[embedding-shape]

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.