| ▲ | embedding-shape 9 hours ago | ||||||||||||||||||||||
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 9 hours ago | parent | next [-] | ||||||||||||||||||||||
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 | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | hirsin 8 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
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. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | oooyay 2 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
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. | |||||||||||||||||||||||
| ▲ | eviks 9 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
> Thank you for your understanding! × 4609 | |||||||||||||||||||||||
| ▲ | sneak 8 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
“Everyone, just STOP PRESSING REPLY-ALL.” It’s not just bots that fall into this trap. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | m0llusk 8 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
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. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | philipwhiuk 8 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
> 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 | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | Sophira 8 hours ago | parent | prev [-] | ||||||||||||||||||||||
> 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. | |||||||||||||||||||||||
| |||||||||||||||||||||||