* using log directory 'd:/Rcompile/CRANpkg/local/4.4/dittodb.Rcheck' * using R Under development (unstable) (2024-03-24 r86185 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'dittodb/DESCRIPTION' ... OK * this is package 'dittodb' version '0.1.7' * 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 'dittodb' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking 'build' directory ... OK * checking DESCRIPTION meta-information ... OK * 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 ... [2s] OK * checking loading without being on the library search path ... [1s] OK * checking whether startup messages can be suppressed ... [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 ... [5s] OK * checking Rd files ... [1s] NOTE checkRd: (-1) mock-db-methods.Rd:139: Lost braces; missing escapes or markup? 139 | how {dittodb} works. | ^ checkRd: (-1) mockdb.Rd:27: Lost braces; missing escapes or markup? 27 | remember to stop the mocking. When testing with {dittodb}, it will look for | ^ checkRd: (-1) mockdb.Rd:41: Lost braces; missing escapes or markup? 41 | that function because {dittodb} uses the database name (given in \code{dbname} or | ^ checkRd: (-1) nycflights_sqlite.Rd:13: Lost braces; missing escapes or markup? 13 | Included with {dittodb} is a small subset of | ^ checkRd: (-1) nycflights_sqlite.Rd:18: Lost braces; missing escapes or markup? 18 | This database is helpful for getting to know {dittodb} and running example | ^ checkRd: (-1) redact_columns.Rd:24: Lost braces; missing escapes or markup? 24 | \code{data} using {dittodb}'s standard redactors. | ^ checkRd: (-1) sanitize_table_id.Rd:20: Lost braces; missing escapes or markup? 20 | drivers. For the purposes of {dittodb}, the details are less important since | ^ checkRd: (-1) set_dittodb_debug_level.Rd:5: Lost braces; missing escapes or markup? 5 | \title{Set {dittodb}'s debug level} | ^ checkRd: (-1) set_dittodb_debug_level.Rd:16: Lost braces; missing escapes or markup? 16 | It can be helpful to see what's going on by increasing {dittodb}'s verbosity | ^ checkRd: (-1) set_dittodb_debug_level.Rd:24: Lost braces; missing escapes or markup? 24 | silent. The higher the level, the more verbose {dittodb} will be. | ^ checkRd: (-1) set_dittodb_debug_level.Rd:26: Lost braces; missing escapes or markup? 26 | Currently, {dittodb} only has one level of debugging (any value 1 or | ^ checkRd: (-1) use_dittodb.Rd:5: Lost braces; missing escapes or markup? 5 | \title{Use {dittodb} in your tests} | ^ checkRd: (-1) use_dittodb.Rd:16: Lost braces; missing escapes or markup? 16 | If you would like to use {dittodb} in your package, and you are already using | ^ checkRd: (-1) use_dittodb.Rd:18: Lost braces; missing escapes or markup? 18 | add {dittodb} to Suggests in the package DESCRIPTION and loads it in | ^ checkRd: (-1) use_dittodb.Rd:24: Lost braces; missing escapes or markup? 24 | \code{path} argument. The function is idempotent: if {dittodb} is already added to | ^ checkRd: (-1) use_dittodb.Rd:29: Lost braces; missing escapes or markup? 29 | \item add {dittodb} to the \code{Suggests} field of the DESCRIPTION file in the | ^ checkRd: (-1) with_mock_path.Rd:23: Lost braces; missing escapes or markup? 23 | database fixtures located in other directories. {dittodb} will look for | ^ * 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 installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... [7s] OK * checking for unstated dependencies in 'tests' ... OK * checking tests ... [30s] OK Running 'spelling.R' [0s] Running 'testthat.R' [29s] * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [9s] OK * checking PDF version of manual ... [21s] OK * checking HTML version of manual ... [4s] OK * DONE Status: 1 NOTE