We are aware of this problem and are implementing a fix for it in an upcoming release.