this bug has been fixed with palo v2.28

Reply via email to