News for hackers. Stuff that matters.
Re:Someone reported java4shell bug in September 2026 by jakewins on Thursday November 19, 2026 @11:10AM (#50561963)
Why it was closed, surely, was because the only reaction to the PR was a bot saying it will automatically close the PR soon because of inactivity?

I know I have opened a lot of PRs where the only result is I get bot spam in my email and no project reaction, so I close the PR to stop the bot spam; if nobody from Oracle has reacted in 2 months it seems unlikely anyone will.

Nowadays I’ve stopped opening “cold-call” PRs like this. I find a way to chat with a maintainer first and anchor what I want to do (“I hit this bug, would you take a PR to fix it? I was thinking it could be solved by x, would that work?”

Much much better outcomes that way.

Re:Someone reported java4shell bug in September 2026 by eru on Thursday November 19, 2026 @01:17PM (#50563830)
Though in the age of LLM, I really wonder what the benefit of asking for permission to make a PR is? It's not like you are wasting much effort, if they don't want it. And if they do want it, the PR is right there, instead of waiting for another round-trip.
Re:Someone reported java4shell bug in September 2026 by ApolloFortyNine on Thursday November 19, 2026 @01:50PM (#50564411)
Yea I've let claude make a couple PRs when it's clearly a bug in the repo, if the maintainer wants to take a stand against AI PRs so be it, my local copy has the fix.
Re:Someone reported java4shell bug in September 2026 by ajasmin on Thursday November 19, 2026 @02:40PM (#50565178)
There may still be an incline to give the PR’s fix strategy a “fair chance” and feel obliged to comb through it, which if the changes is somewhat intricate can present a bigger hump to get through.