Apple randomly closes bug reports unless you "verify" the bug remains unfixed
1–10 of 314 posts
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#2to be fair this is pretty common spring cleaning in any bugzilla...
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#3My favorite is the Claude Code bugtracker, on GitHub of course: https://github.com/anthropics/claude-code/issues
There is some bot that will match your issue to some other 3 vaguely related issue, then auto close in 3 days. The other vaguely related issues are auto closed for inactivity. Nothing is ever fixed, which is why they can't keep the thing from messing with your scroll position for years now.
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#4My favorite is the Claude Code bugtracker, on GitHub of course: https://github.com/anthropics/claude-code/issues There is some bot that will match your issue to some other 3 vaguely related issue, then auto close in 3 days. The other vaguely related issues are auto closed for inactivity. Nothing is ever fixed, which is why they can't keep the thing from messing with your scroll position for years now.
Oh so it jumping to the top happens to others too?
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#5to be fair this is pretty common spring cleaning in any bugzilla...
It's very common but it's still a poor practice.
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#6What else should they do? Stop releasing any updates until they reproduced any obscure bug report?
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#7to be fair this is pretty common spring cleaning in any bugzilla...
I was literally just coming in here to comment "in before someone says this is fine and there's no issue." and the first(!) comment is effectively "this is fine and there's no issue."
The sentiment feels like software folks are optimizing for the local optimum.
It's the programmer equivalent of "if it's important they'll call back." while completely ignoring the real world first and second-order effects of such a policy.
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#8> FB22057274 “Pinned tabs: slow-loading target="_blank" links appear in the wrong tab
If you're not testing your code under extreme latency it will almost certainly fail in all kinds of hilarious ways.
I spend a lot of time with 4G as my only internet connection. It makes me feel that most software is quickly produced, poorly tested, and thrown out the door on a whim.
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#9What else should they do? Stop releasing any updates until they reproduced any obscure bug report?
They could just, not close the bug?
Mozilla is famous for having 20 year old bug reports that gets fixed after all that time.
Re: Apple randomly closes bug reports unless you "verify" the bug remains unfixed
#10My favorite is the Claude Code bugtracker, on GitHub of course: https://github.com/anthropics/claude-code/issues There is some bot that will match your issue to some other 3 vaguely related issue, then auto close in 3 days. The other vaguely related issues are auto closed for inactivity. Nothing is ever fixed, which is why they can't keep the thing from messing with your scroll position for years now.
They are also closing issues automatically that has no "activity" in 30 days, so you have to spam those issues.