Have you considered that the person submitting the PR to fix said problem has themselves experienced it? I find that is most often the case. But there is definitely an increase in the "performance edge cases, or hypotheticals" framing, where I am equally befuddled/too tired.
I had repeated PRs for entirely hallucinated problems.
So yeah, I've considered it and eliminated it for most PRs we used to get. Because no, a 2nd year student in university did not run into an obscure edge case in production that none of my 1M+ QPS users did.
We need the equivalent of that for open source software maintained by people from before 2004.
AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.
Have the AI tooling do the heavy lifting of reproduction and benchmarking. One of my projects is fairly complicated and one user ran into some problems which he could describe the situation that caused it, but was light on any other details: my apt package cache was slow to serve the PHP update to his users. I asked AI to try to reproduce it: Set up a repo, set up different versions of my cache, have a client pull it, put an updated package in there, and have a client pull it again under different configurations. This could have taken me hours to do myself. AI did it with ~2 minutes of my effort.
>I have not organized my life around triaging annoyances
Then don't. AI can help with the triaging. Or, I give you permission: Close the repo for contributions. If you don't have time to maintain it, let people know, so they can fork or replace it. It sounds like your repos are already closed to contributions, due to lack of time/attention. That's fine, don't feel bad, just go ahead and make it official.
For me it was a bit useful but it has not offset even 10% of damage caused by LLMs
and is solving least important problem
You are too nice. Anyone who isn’t going to spend time to explain an issue should be automatically rejected.
As a maintainer of some projects: at this point I would appreciate far more useful review of already submitted PRs.
As long it is not blind copy-pasting LLM output. That would be highly obnoxious attack.
My open source projects were barely sustainable when the few PRs that came in would fix actual, non-hypothetical, serious logic problems.
Now I've been seeing PRs like that, fixing annoyances, performance edge cases, or hypotheticals, across my open source repositories, and I don't have time for them. I especially don't have time to fix problems that probably nobody will ever experience, and yet they keep coming. I have not organized my life around triaging annoyances (let alone fixing them).
If the trend continues, I'll soon be forced to close repositories to contributions, or just stop maintaining the projects entirely. And I imagine that's the point a lot of maintainers are at.