Btw, I just checked the code and there is a patch in branch 5.1 that likely fixed it, seems similar to your report -- can you try with 74b8fbf ? That patch is part of 5.1.7, but you run 5.1.6.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.