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

11–20 of 87 posts

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

#11

Post by embedding-shape »

TACD wrote: post #9
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…

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

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.

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

#14

Post by eviks »

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…

> Thank you for your understanding! × 4609

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

#15

Post by PyWoody »

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.

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

#17

Post by Hamuko »

embedding-shape wrote: post #6
robertclaus wrote: post #3

Classic CI bug with a flair of LLM fun! We had something similar creep into our custom merge queue a few weeks back.

What "classic CI bug" makes bots talk with each other forever? Been doing CI for as long as I've been a professional developer, and not even once I've had that issue. I've made "reply bots" before, bunch of times, first time on IRC, and pretty much the second or third step is "Huh, probably this shouldn't be able to reply to itself, then it'll get stuck in a loop". But that's hardly a "classic CI bug", so don't think…

Yeah, a bot replying to itself is pretty poor design. It's one of the first things you do even with toy bots. You can even hardcode knowing itself, since usually you have an unchanging ID. A much more common problem is if someone deploys another bot, which will lead your bot into having an endless back-and-forth with it.

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

#18

Post by embedding-shape »

Hamuko wrote: post #17
embedding-shape wrote: post #6

Earlier quoted context omitted.

What "classic CI bug" makes bots talk with each other forever? Been doing CI for as long as I've been a professional developer, and not even once I've had that issue. I've made "reply bots" before, bunch of times, first time on IRC, and pretty much the second or third step is "Huh, probably this shouldn't be able to reply to itself, then it'll get stuck in a loop". But that's hardly a "classic CI bug", so don't think…

Yeah, a bot replying to itself is pretty poor design. It's one of the first things you do even with toy bots. You can even hardcode knowing itself, since usually you have an unchanging ID. A much more common problem is if someone deploys another bot, which will lead your bot into having an endless back-and-forth with it.

> A much more common problem is if someone deploys another bot, which will lead your bot into having an endless back-and-forth with it.

This I'd understand, bit trickier since you're basically end up with a problem typical of distributed systems.

But one bot? One identity? One GitHub user? Seems really strange to miss something like that, as you say, it's one of the earlier things you tend to try when creating bots for chats and alike.

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

#19

Post by pinkmuffinere »

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.

lol, that's amazing. Things like this make me both angry (how could they be so dumb!), and empathetic (what is the rest of their life like?)

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

#20

Post by pousada »

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

Post reply on HN