CRAN Package Check Results for Maintainer ‘Davis Vaughan <davis at posit.co>’

Last updated on 2024-07-24 00:54:17 CEST.

Package ERROR NOTE OK
almanac 13
bench 2 11
clock 2 7 4
cpp11 13
decor 13
ivs 13
slider 5 8
treesitter 13
treesitter.r 4 9
tzdb 5 8
vctrs 1 5 7
warp 5 8

Package almanac

Current CRAN status: OK: 13

Package bench

Current CRAN status: NOTE: 2, OK: 11

Version: 1.1.3
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: press.Rd: tibble Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. Flavors: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64

Package clock

Current CRAN status: ERROR: 2, NOTE: 7, OK: 4

Version: 0.7.1
Check: compiled code
Result: NOTE File ‘clock/libs/clock.so’: Found non-API calls to R: ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.7.1
Check: compiled code
Result: NOTE File 'clock/libs/x64/clock.dll': Found non-API calls to R: 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_TRUELENGTH' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Version: 0.7.1
Check: installed package size
Result: NOTE installed size is 18.3Mb sub-directories of 1Mb or more: libs 16.4Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 0.7.1
Check: running R code from vignettes
Result: ERROR Errors in running code in vignettes: when running code in ‘clock.Rmd’ ... > date_build(2019, 2, 1:5) [1] "2019-02-01" "2019-02-02" "2019-02-03" "2019-02-04" "2019-02-05" > date_build(2019, 1:12, 31) When sourcing ‘clock.R’: Error: Invalid date found at location 2. ℹ Resolve invalid date issues by specifying the `invalid` argument. Execution halted when running code in ‘faq.Rmd’ ... <year_month_day<day>[1]> [1] "2019-02-05" > add_days(x, 1) When sourcing ‘faq.R’: Error: Can't perform this operation on a <clock_year_month_day>. ℹ Do you need to convert to a time point first? ℹ Use `as_naive_time()` or `as_sys_time()` to convert to a time point. Execution halted when running code in ‘recipes.Rmd’ ... [6] "2019-11-01" "2020-01-01" "2020-03-01" "2020-05-01" "2020-07-01" > date_seq(date_build(2019, 1, 1), to = date_build(2019, + 10, 2), by = duration_months(2)) When sourcing ‘recipes.R’: Error: All components of `from` and `to` more precise than "month" must match. ℹ `from` is "2019-01-01". ℹ `to` is "2019-10-02". Execution halted ‘clock.Rmd’ using ‘UTF-8’... failed ‘faq.Rmd’ using ‘UTF-8’... failed ‘recipes.Rmd’ using ‘UTF-8’... failed Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Package cpp11

Current CRAN status: OK: 13

Package decor

Current CRAN status: OK: 13

Package ivs

Current CRAN status: OK: 13

Package slider

Current CRAN status: NOTE: 5, OK: 8

Version: 0.3.1
Check: compiled code
Result: NOTE File ‘slider/libs/slider.so’: Found non-API call to R: ‘STRING_PTR’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.3.1
Check: compiled code
Result: NOTE File 'slider/libs/x64/slider.dll': Found non-API call to R: 'STRING_PTR' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Package treesitter

Current CRAN status: OK: 13

Package treesitter.r

Current CRAN status: NOTE: 4, OK: 9

Version: 1.0.1
Check: package dependencies
Result: NOTE Package suggested but not available for checking: ‘treesitter’ Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Package tzdb

Current CRAN status: NOTE: 5, OK: 8

Version: 0.4.0
Check: compiled code
Result: NOTE File ‘tzdb/libs/tzdb.so’: Found non-API calls to R: ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.4.0
Check: compiled code
Result: NOTE File 'tzdb/libs/x64/tzdb.dll': Found non-API calls to R: 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_TRUELENGTH' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Package vctrs

Current CRAN status: ERROR: 1, NOTE: 5, OK: 7

Version: 0.6.5
Check: compiled code
Result: NOTE File ‘vctrs/libs/vctrs.so’: Found non-API calls to R: ‘FRAME’, ‘HASHTAB’, ‘LEVELS’, ‘PRENV’, ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_findVarInFrame3’, ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_ENCLOS’, ‘SET_FORMALS’, ‘SET_GROWABLE_BIT’, ‘SET_S4_OBJECT’, ‘SET_TRUELENGTH’, ‘STDVEC_DATAPTR’, ‘STRING_PTR’, ‘TRUELENGTH’, ‘UNSET_S4_OBJECT’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.6.5
Check: compiled code
Result: NOTE File 'vctrs/libs/x64/vctrs.dll': Found non-API calls to R: 'FRAME', 'HASHTAB', 'LEVELS', 'PRENV', 'PRVALUE', 'R_PromiseExpr', 'Rf_findVarInFrame3', 'SETLENGTH', 'SET_BODY', 'SET_CLOENV', 'SET_ENCLOS', 'SET_FORMALS', 'SET_GROWABLE_BIT', 'SET_S4_OBJECT', 'SET_TRUELENGTH', 'STDVEC_DATAPTR', 'STRING_PTR', 'TRUELENGTH', 'UNSET_S4_OBJECT' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Version: 0.6.5
Check: whether package can be installed
Result: ERROR Installation failed. Flavor: r-oldrel-windows-x86_64

Package warp

Current CRAN status: NOTE: 5, OK: 8

Version: 0.2.1
Check: compiled code
Result: NOTE File ‘warp/libs/warp.so’: Found non-API calls to R: ‘Rf_findVarInFrame3’, ‘STRING_PTR’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.2.1
Check: compiled code
Result: NOTE File 'warp/libs/x64/warp.dll': Found non-API calls to R: 'Rf_findVarInFrame3', 'STRING_PTR' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64