We found a SharePoint bug