This was an issue filed around Oct 25th 2016.  For some reason, the issue description was lost, probably due to a transient error or outage at the time the issue was filed.  I don't know, but I assume that the reporter would have filed a new issue report later.  So, this issue report is probably either duplicate or obsolete.  I'll close it now.  Feel free to reopen if you want.