Closing this issue as the bug has already been resolved. If you encounter this problem again, please let us know by creating a new report.