by embedding-shape
8 subcomments
- 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...
- 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.
by ryandrake
1 subcomments
- 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.
- Script author here :-) This was due to two different GitHub Action workflows:
(Workflow 1): Remove the need-triage label under certain conditions.
(Workflow 2): If anyone outside a project maintainer removes a label, re-add it with a friendly message explaining why.
Submitted those at like 10 or 11 pm and went to sleep. Woke up to all issues that got changed overnight with dozens, hundreds, or thousands of these messages.
Cause: Workflow 2 should have checked for project maintainers but also other bots and automation that might also be clearing labels. It got fixed immediately once we realized the issue.
- This issue seems to involve Gemini-cli[bot] squabbling with itself, adding and removing the label from the issue (leaving contradictory explanation comments to itself each time) for a good 4,600 rounds
- Finally an example of AI doing something useful. Imagine having to add and remove all those tags 4500+ times by hand!
- To be clear, is AI actually at play here, aside from the fact that the repo is for Gemini? It just looks like two simple rules that interact poorly, that we could've seen in 2015.
by robertclaus
1 subcomments
- Classic CI bug with a flair of LLM fun! We had something similar creep into our custom merge queue a few weeks back.
- Maybe I'm missing something, but this seems to be an issue report claiming to be a PR? Where's the patch?
Edit: there's actually a PR, but this is one of those repos where for some reason, they require every PR to have an associated issue. And in this case, they aren't even linked...
by abathologist
0 subcomment
- This will soon be happening with our parents' social security checks, our friend's cancer treatment plan, our international flights logistics, our ISPs routing configurations, ...
Fun times are coming.
by armchairhacker
0 subcomment
- Ironically this is type of issue is common in pre-LLM (rules-based) AI. Given that the back-and-forth messages are the same, I suspect they're generated by a small script, not an LLM. But I wouldn't be surprised if the script was created mostly or entirely by an LLM.
- Today github labels, tomorrow paperclips?
- Project admins setting up automation: https://youtu.be/B4M-54cEduo?t=102
The automation: https://youtu.be/GFiWEjCedzY?t=51
- I think the real irony is an LLM trying to enforce permissions at all. Why is it doing that? If the tag exists, the user had the permission to create it, no?
- 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.
by Phui3ferubus
0 subcomment
- > 4610 remaining items
Normally I would complain about people spamming in GitHub issues but I don't think it will matter this time
- It's not wrong.
by heliumtera
0 subcomment
- So much productivity accomplished here! Those are numbers management loves to see.
gemini-cli did much more work in this PR then the author himself.
by mise_en_place
0 subcomment
- Now that's what I call job security.
by venturecruelty
0 subcomment
- [dead]
Hacker News