This content has been marked as final. Show 2 replies
I'm pretty sure you and I debugged this issue over email. If that was not you, please let me know.
You were hitting a bug in our parser that is fixed in the upcoming 19.3.3 release. Sorry about that.
Yup, it was me.