@WG-prioritization/alerts issue #77188 has been requested for prioritization.
Because there's basically no way to repro this, I'd say
I pinged the author asking for the repo
hmm, I'm not sure reproducibility should affect the priority
if we really think it can't be reproduced maybe it should jsut be closed
otherwise it will be open forever, because we'll never notice if it's fixed
I assumed when they said "can't share", it's not open source
ok, let's wait for a response and if they say they can't share either the original or an MCVE, then close it
There's quite a few
A-incr-comp issues similar to this one. I'm not sure whether it's valuable to leave them all open or perhaps we should deduplicate to one generic issue which links to closed duplicates?
is there one that's reproducible maybe? but I agree there should be at most one open
'whichever has the most info' is normally what I go with
hmm we have lots of issues with similar errors but slightly different stack traces. I'll leave this alone for now and hopefully the author can provide a small repro.
I agree. let's leave it pending for now
Issue #77188's prioritization request has been removed.
Closed. Reopen if you disagree.
is that a dare? :laughing:
No, just saying that we should reopen if people think it's better to leave it open for some reason :)
(I'm trying to triage some older I-prioritize issues)