Closed msberends closed 2 years ago
The solution is easily found on the web, or on github (including this issue). Also it might be a genuine problem with the database, so the simple and generic solution of re-installing the package would not apply.
Given that it's a one-off problem I think we are good as it is :wink:
We had the problem described in #928 and #945:
More specific:
This was caused because we updated R from 4.1.3 to 4.2.1 on Windows; reinstalling
lubridate
solved it as confirmed by others. Would it be an idea to notify the user that this might solve things? It seems that some cache was used bylubridate
or so?We found lots and lots of cases of this error around the internet (here, StackOverflow, RStudio Community). Would be great if future people wouldn't need to search for so long 🙂