Sorry, that's issue 438 instead of 468
Hey, it is opensource. If you can provide us with a fix and a testcase for it, we'd be happy to include it.
hmmm... sorry, the fix seems to be in there. Still, it would be nice if you could provide us with a testcase.
The issues is already reopened by Tom....
I would really love to, at this point I'm swamped with other work. I'll try to get something in next week. The fix has been tested in our performance testing environment so I'm pretty sure of it.
Do I attach the unit test to the issue description?