Thank you for bringing this to our attention 🙂

We cross-checked in 4.34 internal version, bug was still there, not anymore.