It's using region path instead of getting the region. It should be no risk.
On 8/19/20, 10:25 AM, "Xiaojian Zhou" <zho...@vmware.com> wrote: This problem also exists in 1.13.
It's using region path instead of getting the region. It should be no risk.
On 8/19/20, 10:25 AM, "Xiaojian Zhou" <zho...@vmware.com> wrote: This problem also exists in 1.13.