I see the same issue on my end. It’s probably good to file an issue on GitHub. In the meantime, here is a workaround:
