Replies: 2 comments
|
Thanks for reporting. After some searching, it looks like Sys.setlocale("LC_ALL", "en_GB.UTF-8")
envs <- Sys.getenv()? |
0 replies
|
Closing, because I haven't heard back on whether Sys.setlocale("LC_ALL", "en_GB.UTF-8")
envs <- Sys.getenv()alone also give an error, CentOS 7 had End of Life on 2024-06-30, and there is a workaround in case someone runs into this; Sys.setlocale("LC_ALL", "C")FWIW, I could not reproduce this, most recently on Ubuntu 24.04 with R 4.5.2. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I am running some code on our cluster and keep hitting an error about an invalid multibyte string when a function is called with a
future. The following reproduces the error in a fresh session on the cluster:If I set the locale to
"C"the error disappears:SessionInfo:
Details
The error does not appear when I run the code with the
en_GB.UTF-8locale on my MacBook, so I am at a bit of a loss on how to debug this.The obvious fix to just always set
Sys.setlocale('LC_ALL',"C")at the beginning of the script works most of the time, but sometimes the code seems to forget about the setting and still crashes.All reactions