Earlier quoted context omitted.
What if a junior with an LLM did this?
What about an LLM with a junior?
LM?
It looks like the status/need-triage label was removed
81–87 of 87 posts
Re: It looks like the status/need-triage label was removed
#82Script 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 mess…
> Submitted those at like 10 or 11 pm and went to sleep. That's a classic :) Hopefully this hasn't caused any real harm. At least it sure did give me a good laugh when I first saw it.
In corporate, that's pushed to prod and then got on an international flight on a Friday afternoon.
Re: It looks like the status/need-triage label was removed
#83Earlier quoted context omitted.
You become an expert in using SalesForce, or SAP, for the same reason you get a medical license in the US. There’s a limited number of you who are willing to traverse that gauntlet of abuse, so you know you’ll always have work.
For doctors in the US I think the limit is more artificial than that: a cap on how many med school seats are allowed.
The captive audience after some (mostly) arbitrary grinding,
(not being drawn to serve the niche by any particular talent or interest besides $),
is the comparison being drawn.
Re: It looks like the status/need-triage label was removed
#84in 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.
I also start all of my prompts with "solve the halting problem."
Clang manages to have way more useful error messages despite not solving three halting problem. You don't need to solve the halting problem to have caught this problem. Even if you don't solve it for the general case of the halting problem, solving it here for a levels deep and then collapsing the levels would have stopped this problem in its tracks. Sure, someone could just come in and cause the bug at N+1 levels deep because you've only solved it at N, but you can write different tests to mitigate that problem in practice, despite not having infinity RAM *2+1 to solve the general case of the halting problem.
Hilariously, the halting problem has been written in enough of the LLM training data that it can identify some cases where the code won't terminate.
Re: It looks like the status/need-triage label was removed
#85Script 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 mess…
I learned the hard way to always implement a circuit breaker for event-driven triggers like this. We use a simple Redis counter with a short TTL to rate limit execution and fail fast if it detects a loop. It is standard practice in backend queues like Celery but easy to overlook in CI configurations.
Re: It looks like the status/need-triage label was removed
#86It'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
[dead]