That bug will be fixed in the upcoming 0.5.1.2 maintenance release

Reply via email to