02-25-2022, 09:19 PM -
(02-21-2022, 08:08 PM)Ani Wrote: Seems indeed to be a regression, someone needs to bisect and open a regression ticket for the exact build that broke it
When I made my initial post about the bug, it was right after I first discovered it, so I figure that if anyone can provide insight about the build that caused it that'd be me. I don't know what regression and bisection mean in this context, but I hope that I can help despite that. This emulator thankfully logs its update history and it appears that on the 6th of February, which was the day I wrote the post, it updated from (0.0.20-13254) to (0.0.20-13263). Looking at the build history, this leaves a mere four candidates for patient zero. I'll conclude this when I find the earliest instance of that bug.
It's (0.0.20-13263) for sure. Double-checked it. Now with luck, someone knowledgeable will come along and bisect the regression.