-
Notifications
You must be signed in to change notification settings - Fork 62
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
legacy_github() fails to read pins #549
Comments
Could you please provide a reprex, or a traceback from the error? |
Here's the traceback, I'm not really sure how to make a reprex for this situation since I don't really understand the error. The pins have been stored on a separate branch in a private github repo that houses a R package. |
And this is pins 1.0.0, right? The reprex doesn't need to be runnable for me; it's just useful to see the exact sequence of calls that lead to this error. |
Yes, this is pins 1.0.0, but I am using the old API. Here's a reprex:
|
I think my problem is deeper than I thought. I tried adding a new pin to see if that locked, and it completely broke things.
|
I think we can probably just remove the file locking; from my vague memory of looking at the code, I don't think it's likely to work 100% anyway. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Reprex: library(pins)
Sys.setenv(GITHUB_PAT = gitcreds::gitcreds_get(use_cache = FALSE)$password)
board_register_github("test-old-pins", repo = "hadley/test-pins")
pin(iris, board = "test-old-pins") With backtrace:
|
Simpler reprex (after gitcreds integration) library(pins)
board <- legacy_github("hadley/test-pins")
pin(iris, board = board) |
Looks like this was broken in 7cde6e7 — I didn't realise |
* Get GitHub PAT via gitcreds * Encode contents of file, not file path * Fix algorithm for finding registry (since legacy github board uses path for path within repo) Fixes #549
Looks like it was 3 different things that were all slightly broken; should be good to go now. |
Awesome, our workflow is back up and running, thanks so much! |
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. |
I am unable to access pins and receiving this (new to me) error message:
Not use how the files became locked, our team had been using pins to access shared data files for the past year without issue. We're still using the old API due to using the Github board. Any ideas about what is happening here?
The text was updated successfully, but these errors were encountered: