upvote
They closed themselves immediately after the stale bot pinged to say it was going to be closed automatically. If you're not that investigated in a PR for a niche corruption bug, you open it and nobody responds for two months, when you get notified about it it's pretty reasonable to just close and move on. Perfectly normal OSS contributor behaviour imo (especially in this new world where every project is drowning under AI contributions, and struggling to stay responsive).
reply
> you open it and nobody responds for two months, when you get notified about it it's pretty reasonable to just close and move on.

Why invest more time to close it? The automation will do it for you.

In this case, there's evidence from a linked issue that Oracle was in communication with the author outside the PR. When you get a ping, and you know it's being worked on outside the PR, it does make sense to close it, cause you know it's being resolved elsewhere.

reply
For example, not to get another useless notification from a bot later
reply
They knew about the fix coming?
reply
That's my guess. But also opening a public issue was a faux pas.
reply
> But also opening a public issue was a faux pas.

Sorry, but why?

Why should someone discovering a bug in an enormously complex piece of software have any responsibility for assessing the security implications of that bug?

If the maintainers wanted to make it private they could have done so.

reply
Submitter wrote:

> The stub stores past the logical output length before returning to Java, corrupting the heap.

That's obviously a security vulnerability. If they didn't understand that, how did they even find it?

reply
At the time maybe he assumed it was just a crash.
reply
From the report:

> The stub stores past the logical output length before returning to Java, corrupting the heap.

It was obviously a security vulnerability. That the project didn't immediately re-write then close the PR and admonish submitter is astounding.

reply
Given they (those best able to understand the significance of the crash) didn't consider the bug worth fixing, I'm not sure why they'd admonish the submitter. Or why submitters in the future should act more carefully.

The takeaway from this is not "the submitter was wrong", it's "we need to move off of openjdk yesterday".

reply
Assumes facts not in evidence. We do not know that the maintainers "didn't consider the bug worth fixing". And yes, submitters should "act more carefully" when they know they are reporting a vulnerability.
reply