You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
This could be the effect of the issue fixed by commit 7e78723 (pushed in 5.1 couple of days ago, while in master had it since end of February). Can you try using the latest 5.1 branch? A new release in that branch will be done soon.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.