CRAN Package Check Results for Maintainer ‘Andre Leite <leite at castlab.org>’

Last updated on 2025-05-15 07:50:12 CEST.

Package ERROR NOTE OK
BigDataPE 13
diario 10 3
pikchr 13
plug 10 3
RapidFuzz 2 11
webdav 2 11

Package BigDataPE

Current CRAN status: OK: 13

Package diario

Current CRAN status: NOTE: 10, OK: 3

Version: 0.1.0
Check: DESCRIPTION meta-information
Result: NOTE Missing dependency on R >= 4.1.0 because package code uses the pipe |> or function shorthand \(...) syntax added in R 4.1.0. File(s) using such syntax: ‘diario.R’ 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, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64

Package pikchr

Current CRAN status: OK: 13

Package plug

Current CRAN status: NOTE: 10, OK: 3

Version: 0.1.0
Check: DESCRIPTION meta-information
Result: NOTE Missing dependency on R >= 4.1.0 because package code uses the pipe |> or function shorthand \(...) syntax added in R 4.1.0. File(s) using such syntax: ‘plug.R’ 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, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64

Package RapidFuzz

Current CRAN status: NOTE: 2, OK: 11

Version: 1.0
Check: installed package size
Result: NOTE installed size is 6.5Mb sub-directories of 1Mb or more: libs 5.8Mb Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Package webdav

Current CRAN status: ERROR: 2, OK: 11

Additional issues

MKL noLD

Version: 0.1.4
Check: examples
Result: ERROR Running examples in ‘webdav-Ex.R’ failed The error most likely occurred in: > base::assign(".ptime", proc.time(), pos = "CheckExEnv") > ### Name: webdav_create_directory > ### Title: Create a collection (directory) on a WebDAV server > ### Aliases: webdav_create_directory > > ### ** Examples > > > # Example usage with a public WebDAV server. > # Visit test_server$url link to view the results of the operation. > library(magrittr) > library(httr2) > test_server <- "https://www.webdavserver.com/" %>% + request() %>% + req_retry(max_tries = 1, max_seconds = 2, backoff = ~ 1) %>% + req_perform() %>% + try(silent = TRUE) > > # Create a directory on the WebDAV server > if (class(test_server) != "try-error") + webdav_create_directory(base_url = test_server$url, folder_path = "Test_Folder", verbose = TRUE) Folder path to create: Test_Folder Base URL: https://www.webdavserver.com/User8b561bc/Test_Folder Username: Not provided Request object created successfully. No authentication added. Error during directory creation: HTTP 500 Internal Server Error. Error in value[[3L]](cond) : Failed to create directory. Calls: webdav_create_directory ... tryCatch -> tryCatchList -> tryCatchOne -> <Anonymous> Execution halted Flavor: r-release-linux-x86_64

Version: 0.1.4
Check: examples
Result: ERROR Running examples in 'webdav-Ex.R' failed The error most likely occurred in: > ### Name: webdav_download_file > ### Title: Download a file from the WebDAV server > ### Aliases: webdav_download_file > > ### ** Examples > > # Example usage with a public WebDAV server. > library(magrittr) > library(httr2) > test_server <- "https://www.webdavserver.com/" %>% + request() %>% + req_retry(max_tries = 1, max_seconds = 2, backoff = ~ 1) %>% + req_perform() Error in `req_perform()`: ! Failed to perform HTTP request. Caused by error in `curl::curl_fetch_memory()`: ! Timeout was reached [www.webdavserver.com]: Failed to connect to www.webdavserver.com port 443 after 10005 ms: Timeout was reached Backtrace: ▆ 1. ├─... %>% req_perform() 2. └─httr2::req_perform(.) 3. └─httr2:::handle_resp(req, resp, error_call = error_call) 4. └─rlang::cnd_signal(resp) Execution halted Flavor: r-oldrel-windows-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.