An update on this issue.

The error went away once I upgraded WSL to WSL2 on Windows 10. The report renders without error now.