this was fixed in v1.16