Hi Macw0lf,
I just looked into this bug and it is still under assessment by the development staff. I have updated the report to reflect that additional developers are experiencing this error, however I do not have a timeframe of when a fix will be implemented.