Skip to content

Cryptic error in gh actions when lockfile creation failed (caused by malformed DESCRIPTION) #632

@olivroy

Description

@olivroy

I don't really know how this happened.

I get the same locally with pak::lockfile_create()...

My imports are

Imports:
    bigD,
    commonmark
    readr,
    dplyr,
    gt,
    janitor,
    lubridate,
    parsedate,
    pkgload,
    plotly,
    quarto,
    rlang (>= 1.1.0),
    rvest,
    stringr,
    tidyr,
    usethis,
    yaml

in DESCRIPTION

Creating lockfile '.github/pkg.lock' [759ms]
  
  
  Error: 
  ! error in pak subprocess
  Caused by error in `if (any(bad <- types == "")) { …`:
  ! missing value where TRUE/FALSE needed
  ---
  Backtrace:
  1. pak::lockfile_create(c(deps, extra_deps), lockfile = ".github/pkg.lock", …
  2. pak:::remote(function(...) { …
  3. err$throw(res$error)
  ---
  Subprocess backtrace:
   1. base::withCallingHandlers(cli_message = function(msg) { …
   2. get("lockfile_create_internal", asNamespace("pak"))(...)
   3. prop$solve()
   4. private$plan$solve(policy = private$policy)
   5. pkgdepends:::pkgplan_solve(self, private, match.arg(policy))
   6. self$resolve()
   7. pkgdepends:::pkgplan_resolve(self, private)
   8. pkgdepends:::synchronise(self$async_resolve())
   9. asNamespace("pkgcache")$synchronise(...)
  10. base::stop(priv$value)
  11. global (function (e) …
  Execution halted

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions