CRAN Package Check Results for Package dpdr

Last updated on 2026-03-05 19:51:17 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-gcc 0.1.0 2.31 24.15 26.46 ERROR
r-devel-linux-x86_64-fedora-clang 0.1.0 53.00 OK
r-devel-linux-x86_64-fedora-gcc 0.1.0 51.43 OK
r-devel-macos-arm64 0.1.0 1.00 17.00 18.00 OK
r-devel-windows-x86_64 0.1.0 7.00 120.00 127.00 OK
r-patched-linux-x86_64 0.1.0 2.96 27.43 30.39 OK
r-release-macos-arm64 0.1.0 1.00 16.00 17.00 OK
r-release-macos-x86_64 0.1.0 2.00 87.00 89.00 OK
r-release-windows-x86_64 0.1.0 7.00 69.00 76.00 OK
r-oldrel-macos-arm64 0.1.0 1.00 72.00 73.00 OK
r-oldrel-macos-x86_64 0.1.0 2.00 57.00 59.00 OK
r-oldrel-windows-x86_64 0.1.0 7.00 114.00 121.00 OK

Check Details

Version: 0.1.0
Check: examples
Result: ERROR Running examples in ‘dpdr-Ex.R’ failed The error most likely occurred in: > base::assign(".ptime", proc.time(), pos = "CheckExEnv") > ### Name: dpd_active_ingredient > ### Title: Active Ingredient > ### Aliases: dpd_active_ingredient > > ### ** Examples > > dpd_active_ingredient(id = 48905) Error in `httr2::req_perform()`: ! HTTP 500 Internal Server Error. Backtrace: ▆ 1. ├─dpdr::dpd_active_ingredient(id = 48905) 2. │ ├─base::withVisible(eval(mc, parent.frame())) 3. │ └─base::eval(mc, parent.frame()) 4. │ └─base::eval(mc, parent.frame()) 5. └─dpdr (local) `<fn>`(id = 48905) 6. └─httr2::req_perform(req) 7. └─httr2:::handle_resp(req, resp, error_call = error_call) 8. └─httr2:::resp_failure_cnd(req, resp, error_call = error_call) 9. ├─rlang::catch_cnd(...) 10. │ ├─rlang::eval_bare(...) 11. │ ├─base::tryCatch(...) 12. │ │ └─base (local) tryCatchList(expr, classes, parentenv, handlers) 13. │ │ └─base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]]) 14. │ │ └─base (local) doTryCatch(return(expr), name, parentenv, handler) 15. │ └─base::force(expr) 16. └─rlang::abort(...) Execution halted Flavor: r-devel-linux-x86_64-debian-gcc

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.