Comment Re:I've noticed that too (Score 1) 54
The report included a patch, but the patch was completely wrong based on a random guess of how a certain software could behave. It 'worked' for the reporter by also swallowing all errors and silently continuing, despite the particular call failing. It was a check to see if a particular action would be needed, and so it silently assumed the step would not be needed, which happened to be true for the reporter so it looked 'fixed' to them.
Problem is that there are more than two people that are stakeholders, and and it would be nuts for me to just let the codebase get screwed up to try to prove a point for one very minor stakeholder who won't even get bitten by the mistake because their situation doesn't hit the bug inflicted by the change. If I let a random user patch a codebase, I rightfully get blamed, not them. And AI assessment of the report would likely agree with the submitter, because the AI generated a plausible rationale, and AI gives the benefit of the doubt to the material in the prompt fodder.
There actually is a project that I used to be a part of but no longer use or work on, but left my notifications active, because why bother changing and it was largely a "done" project, almost no new issues, not much in terms of code changes. Some guy decided to go all in on LLM giving free reign. Was not confident to be a developer but declared AI made it possible for him to change things. Suddenly lots of code changes, and also a sudden flurry of external issues of users who had been using it for a long time asking why random stuff was broken. Near as I could tell when I got around to disabling all the notifications, he just kept feeding issues into LLM and releasing updates and getting a new wave of issues and repeating. What was a boringly stable project became an eternally random messed up mess because he let LLM take over everything and it breaks as much as it helps. I'm not letting any of my active projects turn into that.