Yes, that was fixed in master but not backported to v6-26-00-patches until yesterday. Sorry about that