"Possible close" issues audit

For people working on the C++ code.
Post Reply
User avatar
Zughy
Member
Posts: 301
Joined: Thu Mar 26, 2020 18:23
GitHub: belongs_to_microsoft
In-game: Zughy
Location: Italy
Contact:

"Possible close" issues audit

by Zughy » Post

I've closed as many "possible close" issues as possible, but some of them require core devs take. It follows a summary:

#12108: need feedback on latest comment about whether to close it or not

#11829: either "won't fix" and close, or actually fix it

#11742: need feedback

#8977: (4 aug 2021) problem reduced but not completely gone. Have some PRs improved the situation in the meanwhile? If yes, close, if not, either remove "possible close" or ask for a more specific issue

#5013: sounds obscure, as the latest comment says they can't reproduce it on 5.4.1+ (5.6.0-dev version included), but the same person in the previous comment also says that it appeared in 5.4.1+ two days earlier (but not 5.6.0-dev). What?

#1566: need feedback

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests