Closed juliasilge closed 2 years ago
This is now fixed via #642
library(pins)
b <- board_temp(versioned = TRUE)
b %>% pin_write(head(mtcars), "mtcars")
#> Guessing `type = 'rds'`
#> Creating new version '20220902T174120Z-209d4'
#> Writing to pin 'mtcars'
Sys.sleep(5)
b %>% pin_write(tail(mtcars), "mtcars")
#> Guessing `type = 'rds'`
#> Creating new version '20220902T174125Z-3fd04'
#> Writing to pin 'mtcars'
b %>% pin_versions("mtcars")
#> # A tibble: 2 × 3
#> version created hash
#> <chr> <dttm> <chr>
#> 1 20220902T174120Z-209d4 2022-09-02 11:41:20 209d4
#> 2 20220902T174125Z-3fd04 2022-09-02 11:41:25 3fd04
Created on 2022-09-02 with reprex v2.0.2
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
For
board_temp()
, the datetimecreated
variable doesn't seem to track along withversion
and is always the same:Created on 2022-05-15 by the reprex package (v2.0.1)
I am running into this for vetiver docs, and you can also see it in the pins docs.