Yea, Fencer knows about the bug, but the last I heard is that the database admistrator (Liquid) was not around to "completly" fix the problem. Fencer has fixed it for now, but he does not guarentee that it will not be back until Liquid is able to take a look at it.