I've been on vacation in the last week, so don't worry, it's not lost. The previous "fix" was reverted in the upstream in the last week, so we need to rework on the proper fix again, in anyway. Please wait for a while until I process backlogs and catch up.