Shall this be closed? The bug was originally reported for v0.5 and we are now on v0.11

Reply via email to