Hello,

I can confirm the issue persists in upstream release 2.2.4 as well.

Andrius

Reply via email to