This issue has been fixed upstream in the 2.011 version.

Regards,
Salvatore

Reply via email to