Unable to install from GitHub. about performance HOT 5 CLOSED

Ahhhh, that did it. I had the CRAN versions of bayestestR and insight, and not the github versions. Silly that I didn't even think of that. Thanks all, for the help (and for these excellent packages which make my life easier)!

from performance.

Dear @ajkroeg, thanks for reporting. I think your issue is related to an update of bayestestR. Could you update it (devtools::install_github("easystats/bayestestR")) before trying installing performance? Thank you!

from performance.

Easystats-packages on GitHub are currently developing very fast, because they're in an early stage. That's why you have to consider the "dependency chain" when installing from GitHub (in order to use new features). Thus, it is recommended to install in following order:

1. insight
2. bayestestR
3. performance
4. parameters / other packages / ...

insight was just updated on CRAN, so you most likely can rely on the CRAN version for insight.

from performance.

Hello again,

Similar problem, different specifics. Everything installs correctly from github (made sure I've got the most recent builds). However, when trying to load library(performance), I get the following error:

> library(performance)
Error: package or namespace load failed for ‘performance’ in get(method, envir = home):
 lazy-load database 'D:/R/R-3.6.0/library/performance/R/performance.rdb' is corrupt
In addition: Warning messages:
1: In .registerS3method(fin[i, 1], fin[i, 2], fin[i, 3], fin[i, 4],  :
  restarting interrupted promise evaluation
2: In get(method, envir = home) :
  restarting interrupted promise evaluation
3: In get(method, envir = home) : internal error -3 in R_decompress1

I've tried uninstalling all the easystats packages and re-installing from github, both individually, and by installing the easystats package itself. I've also tried uninstalling all the easystats packages, and reinstalling from CRAN. Same error for everything.

I know you are constantly updating these, so some install errors are probably inevitable. I can certainly just wait for further updates and not reopen this issue if you like.

from performance.

Perfect. Latest version of bayestestR (the update from v0.1.9.9000 to 0.2.0) took care of it. Thanks!

from performance.