I can confirm this issue has been fixed by release v7.2.0-4-20180606.
Thanks for the impressively fast turnaround @ilg !
I can confirm this issue has been fixed by release v7.2.0-4-20180606.
Thanks for the impressively fast turnaround @ilg !
you’re welcome!