Hi,
unfortunately we don't have enough resources to fix this before 1.0.1 RC4. You could try to send a message to the developer mailing list and see if someone can help with this bug.
Sorry, DIego