For more information, if I downgraded to 4.4.2 this particular problem is fixed. So it must have been introduced in 4.4.3
I'll update when I've grabbed the latest master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.