You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most recent release of pillar seems to coincide with errors on recent package deployments across GitHub Pages. Calling library(dplyr) in a pkgdown article is enough to return the following error:
#> Error in get(paste0(generic, ".", class), envir = get_method_env()) :
#> object 'type_sum.accel' not found
There's some good and bad here. The error doesn't stop deployment, which is good. But the error does silently print on pkgdown pages that don't hide library calls behind an include=FALSE chunk option in RMarkdown, and that's bad, because it can be hard to notice. Here's a sampling of some recently updated project pages that show the problem (as of 23-12-2024):
Thanks for the report! The type_sum.accel() method is needed only for one help page, I'm working around with registering the method only for the help page.
Trying to sneak in an update, but this may need to wait until early January.
The most recent release of pillar seems to coincide with errors on recent package deployments across GitHub Pages. Calling
library(dplyr)
in a pkgdown article is enough to return the following error:There's some good and bad here. The error doesn't stop deployment, which is good. But the error does silently print on pkgdown pages that don't hide library calls behind an
include=FALSE
chunk option in RMarkdown, and that's bad, because it can be hard to notice. Here's a sampling of some recently updated project pages that show the problem (as of 23-12-2024):My best guess is that the problem was introduced by 6f6565b since it wasn't a problem before pillar's most recent CRAN update.
The text was updated successfully, but these errors were encountered: