That's a 4.1.6 (patched with #26), but I believe I checked master when looking into the source why this happens.

Thanks for the feedback. Now I'll "just" have to reliably reproduce this first :)

—
Reply to this email directly or view it on GitHub.