Brice Goglin wrote: > In you missed it, the fix has been backported to 3.3.3 and 3.2.16. Thanks for making it happen. Sincerely, Jonathan