Hey there.
Thanks for the report. This was already reported here:
And a fix should be deployed on SonarQube Cloud relatively soon.