I couldn't reproduce it with 1.7.1 either. If you are positive that the issue is gone, you can close the bug.