Yeah, I tested in bc76f5ac4. Attached is a regression test I composed. I tested it locally and it can catch this bug before 1aa8dad41 and give the expected answer after 1aa8dad41.
It looks like the issue has been found, nice! So I'm wondering: which release will this fix be included (so we can mark the workaround with an end date).