Skip to content
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

[EEXIST] Error While Attempting To Read In pins Data #598

Closed
rmccombie opened this issue Feb 9, 2022 · 2 comments
Closed

[EEXIST] Error While Attempting To Read In pins Data #598

rmccombie opened this issue Feb 9, 2022 · 2 comments

Comments

@rmccombie
Copy link

While attempting to read in pins data, the following error is received:

> data_ed <- pin_read(board = board_rsconnect(), name = "et18378/data_ed_dt")
Connecting to RSC 2021.09.0 at <https://server_name>
Error: [EEXIST] Failed to copy '/tmp/RtmpJvpYRv/file33931451cd351' to '/home/et18378/.cache/pins/rsc-e62371cfd77db754024f9c5ed3556a73/0102056a-79ba-4c51-b81c-f386b6204d9e/203/data.txt': file already exists

Directory listing:

ls -la /home/et18378/.cache/pins/rsc-e62371cfd77db754024f9c5ed3556a73/0102056a-79ba-4c51-b81c-f386b6204d9e/203/
total 20
drwxr-xr-x+ 2 et18378 domain users 4096 Jan 27 09:56 .
drwxr-xr-x+ 4 et18378 domain users 4096 Jan 27 09:56 ..
-r--r--r--+ 1 et18378 domain users  187 Jan 27 09:56 data.txt

(Ticket ref: 70914)

@juliasilge
Copy link
Member

In #667 we changed the Connect content cache over to use environments (instead of files on disk). This means that:

  • caches will not persist between sessions
  • caches will only get into a broken state like this if a big change is made with the server while a user is working with pins from R
  • caches can be fixed by restarting R
  • the first time functions are called they will be slow, but subsequent calls will have the same benefits of caching as we had originally

Thanks again for the report! 🙌 For now, the user will need to install from GitHub to have these improvements but we will do a release soon.

@github-actions
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants