* using log directory 'd:/Rcompile/CRANpkg/local/4.6/puremoe.Rcheck' * using R Under development (unstable) (2025-07-26 r88458 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.2.0 GNU Fortran (GCC) 14.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'puremoe/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'puremoe' version '1.0.2' * package encoding: UTF-8 * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... OK * checking if there is a namespace ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'puremoe' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking DESCRIPTION meta-information ... 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: 'source_pmc.R' 'source_pubmed.R' 'source_pubtations.R' * checking top-level files ... OK * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking code files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... [1s] OK * checking whether the package can be loaded with stated dependencies ... [1s] OK * checking whether the package can be unloaded cleanly ... [1s] OK * checking whether the namespace can be loaded with stated dependencies ... [1s] OK * checking whether the namespace can be unloaded cleanly ... [1s] OK * checking loading without being on the library search path ... [1s] OK * checking use of S3 registration ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... [4s] OK * checking Rd files ... [0s] OK * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking examples ... [25s] ERROR Running examples in 'puremoe-Ex.R' failed The error most likely occurred in: > ### Name: get_records > ### Title: Retrieve Data from 'NLM'/'PubMed' databases Based on PMIDs > ### Aliases: get_records > > ### ** Examples > > pmids <- c("38136652") > results <- get_records(pmids, endpoint = "pubmed_abstracts", cores = 1) Error : HTTP failure: 500
Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error : HTTP failure: 500Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:
pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services
Thank you for your assistance. We will try to fix the problem as soon as possible.
Diagnostic Information:
NOTE: The above is an internal URL which may differ from the one you used to address the page.
Rev. 01/04/08
Error in UseMethod("read_xml") : no applicable method for 'read_xml' applied to an object of class "try-error" Calls: get_records ... FUN -> task_function -> .fetch_records ->