Closed amashadihossein closed 3 years ago
The new board_s3()
no longer maintains a data.txt
because of exactly this problem.
Ok great! Thanks @hadley! I am looking fwd to updating to the new pins and based on the anticipated changes I am planning to set aside some time for the upgrade to the pkg I have built when the new version is released.
Meanwhile, a quick solution seemed to be calling pin_versions
prior to any pinning. I have not seen any cases that this temporary solution hasn't worked, but I wanted to confirm based on your understanding of the problem, does this sound right to you? If so, would it be included in legacy_datatxt
or the idea of legacy_datatxt
is to preserve the current functionality as is?
Thanks!
I have no idea, sorry — I'd have to carefully re-read and analyse the existing code to understand why that works, and it's unlikely I'll have the time to do so.
I understand. Thanks!
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.
cars[1:5,]
from default cache andcars[2+(1:5),]
from another cache path. Then try to get the versions.pin_versions
orpin_get
Note: both datasets remain available on S3 and structured properly under
_version/
path, but data.txt only shows the latest. In other word, the issue is with data.txt keeping accurate records.To repro: