Thank you for the report, that’s a known issue of version 3.8.6. The next release will fix it of course.