Bullitt
February 10, 2024, 9:24am
267
We were talking about this bug over in the test thread and I posted this there. Don’t know if this was discussed here:
@engineer_comp_geek made the initial post:
It’s actually a bug in Discourse. It used to work properly, until it didn’t.
Oh yeah right. I remember when it used to work, and then I also remember around the time it first broke. That was some time back.
If I, or anyone else, can remember when that happened, that information would be very valuable to the Discourse developers in determining what code change(s) caused the break.
I used to be a system test engineer, and that is some of the most tedious work: load SW v37.095 and test it. No…
Oh yeah right. I remember when it used to work, and then I also remember around the time it first broke. That was some time back.
If I, or anyone else, can remember when that happened, that information would be very valuable to the Discourse developers in determining what code change(s) caused the break.
I used to be a system test engineer, and that is some of the most tedious work: load SW v37.095 and test it. No bug? OK, then load SW v37.096 and test it. No bug? OK, then load…
Lather, rinse, repeat. It’s a PITA but sometimes it’s the only way. Especially for older bugs.
Of course, the developers could also scrutinize the code to find the bug, but that too can be very tedious work.
Yeah, it’s a PITA.
If anyone remembers around when the bug first occurred, or ideally provide the link to the post when it first occurred, that would probably help the Discourse SW team.