This exception occurs from 20.06.2012, and I just now understand how to fix it properly (seems badly written cache caused it, as expected), sorry for inconveniences (but seems this exception doesn't affect usability).
I hope next nightly will not contain this exception, but I'm not sure, because I can't reproduce it (I even have never seen it).
This exception occurs from 20.06.2012, and I just now understand how to fix it properly (seems badly written cache caused it, as expected), sorry for inconveniences (but seems this exception doesn't affect usability).
I hope next nightly will not contain this exception, but I'm not sure, because I can't reproduce it (I even have never seen it).
Best regards,
Alexander Podkhalyuzin.