Le 2018-06-25 15:34, Michal Prívozník a écrit :
Should be fixed in 1.2.11 by
6085d917d5c5839b7ed351e99fadbbb56f5178fe.
Upgrade and the bug should go away.
Thanks.
I did see this bug report but didn't understand the description and
didn't think it applied to my use case. Besides, I noticed it was a bit
old (2014) but didn't realize I was using a version _that_ old.
I upgraded to a more recent version (3.0.0) and from a quick test it
works correctly.
Sorry for bothering you with that old issue.
Have a nice day.
--
Jérôme