This issue has indeed been fixed. However, the fixed version will be released after the other fixes have been completed, so we hope you will wait a while before releasing it. (The fix is not in the just released 4.2.15-beta, but will be in the 4.2.16-beta).
