Marking this as fixed release as I cannot reproduce this issue using the new 3.5.9 packages and seeing as the upstream changes from all reports have been included in our packages. Thank you.
Marking this as fixed release as I cannot reproduce this issue using the new 3.5.9 packages and seeing as the upstream changes from all reports have been included in our packages. Thank you.