This should be fixed in repository (revision 63772).
The correction will be available in next release.