Looks like the oobabooga developer was the one who caused this Unicode issue.
Refactored the fix from the last pull request to enable it only when case it's actually needed. I don't trust developers who do everything on the main branch all the time not repeatedly causing this, so the bugfix is only applied when needed.
This commit ensures that this never happens either:
We want to see this:
Obviously, this isn't that bad compared to the situation from 2 days ago when the issue caused bot failures.
Looks like the oobabooga developer was the one who caused this Unicode issue.
Refactored the fix from the last pull request to enable it only when case it's actually needed. I don't trust developers who do everything on the main branch all the time not repeatedly causing this, so the bugfix is only applied when needed.
This commit ensures that this never happens either:
We want to see this:
Obviously, this isn't that bad compared to the situation from 2 days ago when the issue caused bot failures.