packrat::restore(dry.run=TRUE) prints too much on linux
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
This has crashed my Windows 10 x64 RStudio a couple of times when running a linux R session through the terminal via ssh.
I'm on packrat * 0.4.8-53 2017-12-18 Github (rstudio/packrat@708cd13)
Some sample (unwanted) output from packrat::restore(dry.run=TRUE):
$pkgRecords[[130]]$depends[[24]]$depends[[9]]$depends[[4]]
$pkgRecords[[130]]$depends[[24]]$depends[[9]]$depends[[4]]$name
[1] "rlang"
$pkgRecords[[130]]$depends[[24]]$depends[[9]]$depends[[4]]$source
[1] "CRAN"
$pkgRecords[[130]]$depends[[24]]$depends[[9]]$depends[[4]]$version
[1] "0.1.4"
$pkgRecords[[130]]$depends[[24]]$depends[[9]]$depends[[4]]$hash
[1] "fef2abdadbb8db061b9d37e7ca5cb0b4"
$pkgRecords[[130]]$depends[[24]]$depends[[9]]$depends[[4]]$depends
list()
$pkgRecords[[130]]$depends[[25]]
$pkgRecords[[130]]$depends[[25]]$name
[1] "xml2"
$pkgRecords[[130]]$depends[[25]]$source
[1] "CRAN"
$pkgRecords[[130]]$depends[[25]]$version
[1] "1.1.1"
$pkgRecords[[130]]$depends[[25]]$hash
[1] "b531448e498836e5eafe026e2d355c8b"
$pkgRecords[[130]]$depends[[25]]$depends
$pkgRecords[[130]]$depends[[25]]$depends[[1]]
$pkgRecords[[130]]$depends[[25]]$depends[[1]]$name
[1] "BH"
$pkgRecords[[130]]$depends[[25]]$depends[[1]]$source
[1] "CRAN"
$pkgRecords[[130]]$depends[[25]]$depends[[1]]$version
[1] "1.65.0-1"
$pkgRecords[[130]]$depends[[25]]$depends[[1]]$hash
[1] "95f62be4d6916aae14a310a8b56a6475"
$pkgRecords[[130]]$depends[[25]]$depends[[1]]$depends
list()
$pkgRecords[[130]]$depends[[25]]$depends[[2]]
$pkgRecords[[130]]$depends[[25]]$depends[[2]]$name
[1] "Rcpp"
$pkgRecords[[130]]$depends[[25]]$depends[[2]]$source
[1] "CRAN"
$pkgRecords[[130]]$depends[[25]]$depends[[2]]$version
[1] "0.12.15"
$pkgRecords[[130]]$depends[[25]]$depends[[2]]$hash
[1] "a419463fc86b3ecc7338ae3ac3bbb268"
$pkgRecords[[130]]$depends[[25]]$depends[[2]]$depends
list()
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing packrat::restore(dry.run=TRUE) in a Linux R session, using the dependency-structure output shown in the issue as the symptom to investigate. Trace the dry-run output path and determine why the internal package records are printed. Done means the dry run no longer emits that unwanted structure while retaining its intended output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100