-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
collateral not on cran anymore? #18
Comments
Hi Matthieu, I'm afraid I've been a little slow getting the next Collateral release up on CRAN. I've received advice about the issue you're seeing (it's linked to the tibble 1.0 and dplyr 1.0 releases) but should have a simple fix that I'm hoping to test and submit to CRAN this week. I'm sorry for the disruption! |
Update: I've made these fixes and pushed them to |
I tried with the dev version, and still am getting the error message. I would not be surorised if it came from updates in library(tidyverse)
library(collateral)
sessionInfo()
#> R version 4.0.0 (2020-04-24)
#> Platform: x86_64-pc-linux-gnu (64-bit)
#> Running under: Ubuntu 20.04 LTS
#>
#> Matrix products: default
#> BLAS: /usr/lib/x86_64-linux-gnu/atlas/libblas.so.3.10.3
#> LAPACK: /usr/lib/x86_64-linux-gnu/atlas/liblapack.so.3.10.3
#>
#> locale:
#> [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
#> [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8
#> [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
#> [7] LC_PAPER=en_US.UTF-8 LC_NAME=C
#> [9] LC_ADDRESS=C LC_TELEPHONE=C
#> [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
#>
#> attached base packages:
#> [1] stats graphics grDevices utils datasets methods base
#>
#> other attached packages:
#> [1] collateral_0.5.0.9001 forcats_0.5.0 stringr_1.4.0
#> [4] dplyr_0.8.5 purrr_0.3.4 readr_1.3.1
#> [7] tidyr_1.0.3 tibble_3.0.1 ggplot2_3.3.0
#> [10] tidyverse_1.3.0
#>
#> loaded via a namespace (and not attached):
#> [1] tidyselect_1.1.0 xfun_0.13 haven_2.2.0 lattice_0.20-41
#> [5] colorspace_1.4-1 vctrs_0.3.0 generics_0.0.2 htmltools_0.4.0
#> [9] yaml_2.2.1 rlang_0.4.6 pillar_1.4.4 glue_1.4.1
#> [13] withr_2.2.0 DBI_1.1.0 dbplyr_1.4.3 modelr_0.1.7
#> [17] readxl_1.3.1 lifecycle_0.2.0 munsell_0.5.0 gtable_0.3.0
#> [21] cellranger_1.1.0 rvest_0.3.5 evaluate_0.14 knitr_1.28
#> [25] fansi_0.4.1 highr_0.8 broom_0.5.6 Rcpp_1.0.4.6
#> [29] scales_1.1.1 backports_1.1.7 jsonlite_1.6.1 fs_1.4.1
#> [33] hms_0.5.3 digest_0.6.25 stringi_1.4.6 grid_4.0.0
#> [37] cli_2.0.2 tools_4.0.0 magrittr_1.5 crayon_1.3.4
#> [41] pkgconfig_2.0.3 ellipsis_0.3.1 xml2_1.3.2 reprex_0.3.0
#> [45] lubridate_1.7.8 assertthat_0.2.1 rmarkdown_2.1 httr_1.4.1
#> [49] R6_2.4.1 nlme_3.1-147 compiler_4.0.0
packageVersion("collateral")
#> [1] '0.5.0.9001'
iris %>%
nest(data=-Species) %>%
mutate(mean=map_safely(data, ~mean(.$Petal.Length))) %>%
filter(has_errors(mean))
#> Error: Input must be a vector, not a `safely_mapped` object. Created on 2020-05-26 by the reprex package (v0.3.0) |
@MatthieuStigler I haven't been able to replicate this with my packages updated, but I am getting other warnings crop up: > iris %>% nest(data = -Species)
# # A tibble: 3 x 2
# Species data
# <fct> <list>
# 1 setosa <tibble [50 x 4]>
# 2 versicolor <tibble [50 x 4]>
# 3 virginica <tibble [50 x 4]>
# Warning message:
# `...` is not empty.
#
# We detected these problematic arguments:
# * `needs_dots`
#
# These dots only exist to allow future extensions and should be empty.
# Did you misspecify an argument? |
Update: ah, this appears to be a problem in
I've attached my session info below 😊 This will likely be my CRAN release candidate, as I'm keen to fill the void following my tardiness! My session info below—I'm not sure that we've quite isolated this between the updates to
|
Thanks for checking James!! Indeed, after updating all packages, and once getting the current version of collateral, I don't have the problem anymore, youhou!! Thanks! |
Phew! I'll get this sent off to CRAN ASAP 😁 |
Hi
I just noticed collateral is not on cran anymore. I am also facing issues using
has_errors
, such as: rror: Input must be a vector, not asafely_mapped
object. Are these issues linked? Maybe the latter is linked to the developments in the vctrs package? What is the status anyway of the package?Thanks!
The text was updated successfully, but these errors were encountered: