The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.

CRAN Package Check Results for Package locateip

Last updated on 2026-08-20 11:54:15 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1.2 3.66 37.06 40.72 NOTE
r-devel-linux-x86_64-debian-gcc 0.1.2 2.57 29.95 32.52 NOTE
r-devel-linux-x86_64-fedora-clang 0.1.2 26.74 NOTE
r-devel-linux-x86_64-fedora-gcc 0.1.2 26.09 NOTE
r-devel-windows-x86_64 0.1.2 6.00 59.00 65.00 NOTE
r-patched-linux-x86_64 0.1.2 3.31 32.97 36.28 NOTE
r-release-linux-x86_64 0.1.2 3.74 32.93 36.67 NOTE
r-release-macos-arm64 0.1.2 1.00 13.00 14.00 NOTE
r-release-macos-x86_64 0.1.2 3.00 42.00 45.00 NOTE
r-release-windows-x86_64 0.1.2 8.00 0.00 8.00 ERROR
r-oldrel-macos-arm64 0.1.2 NOTE
r-oldrel-macos-x86_64 0.1.2 3.00 41.00 44.00 NOTE
r-oldrel-windows-x86_64 0.1.2 9.00 61.00 70.00 NOTE

Check Details

Version: 0.1.2
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: ‘locate.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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 0.1.2
Check: examples
Result: ERROR Running examples in 'locateip-Ex.R' failed The error most likely occurred in: > ### Name: locate_ip > ### Title: Locate an IP adress > ### Aliases: locate_ip > > ### ** Examples > > locate_ip("132.203.167.188") Error in `httr2::req_perform()`: ! Failed to perform HTTP request. Caused by error in `curl::curl_fetch_memory()`: ! Timeout was reached [ip-api.com]: Resolving timed out after 10011 milliseconds Backtrace: ▆ 1. └─locateip::locate_ip("132.203.167.188") 2. └─locateip:::get_location(...) 3. └─httr2::req_perform(...) 4. └─httr2:::handle_resp(req, resp, error_call = error_call) 5. └─rlang::cnd_signal(resp) Execution halted Flavor: r-release-windows-x86_64

Version: 0.1.2
Check: tests
Result: ERROR Running 'testthat.R' [13s] Running the tests in 'tests/testthat.R' failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/tests.html > # * https://testthat.r-lib.org/reference/test_package.html#special-files > > library(testthat) > library(locateip) > > test_check("locateip") Saving _problems/test-locate-35.R [ FAIL 1 | WARN 2 | SKIP 0 | PASS 8 ] ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test-locate.R:32:3'): locate ip works ─────────────────────────────── <httr2_failure/httr2_error/rlang_error/error/condition> Error in `httr2::req_perform(create_req(ip = ip, fields = fields, lang = lang, header = header, ..., format = format))`: Failed to perform HTTP request. Caused by error in `curl::curl_fetch_memory()`: ! Timeout was reached [ip-api.com]: Resolving timed out after 10015 milliseconds Backtrace: ▆ 1. ├─testthat::expect_equal(...) at test-locate.R:32:3 2. │ └─testthat::quasi_label(enquo(object), label) 3. │ └─rlang::eval_bare(expr, quo_get_env(quo)) 4. └─locateip::locate_ip("132.203.167.188", tidy = TRUE) 5. └─locateip:::get_location(...) 6. └─httr2::req_perform(...) 7. └─httr2:::handle_resp(req, resp, error_call = error_call) 8. └─rlang::cnd_signal(resp) [ FAIL 1 | WARN 2 | SKIP 0 | PASS 8 ] Error: ! Test failures. Execution halted Flavor: r-release-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.