-
Notifications
You must be signed in to change notification settings - Fork 27
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
Subset issues when using piggyback
and renv
#70
Comments
the problem is specifically |
Well, as I understand, |
Interesting! Can you try using |
I have tried this but no luck: > pb_releases(repo = gh::gh_tree_remote())
Error in strsplit(repo, "/") : non-character argument |
Oh. Duh, it returns a list. But at least it returns something! I suspect the problem is that renv only caches the import dependencies so when guess_repo tries to use gert it fails somehow. |
If I install Line 51 in 4b7cdb9
returns a Then, subsetting a data.frame here: remotes[remotes[["name"]] == remote, "url"][["url"]] does not work since |
Oh so it just needs to be remotes$url[remotes$name == remote] then… I wonder if that’s better or worse than shortening dependencies and using gh here for that too |
Exactly!
Good question :) |
Data frame subsetting works if tibble is not installed (closes #70).
I have found multiple issues when using
piggyback
withrenv
enabled project that are likely linked to how subset works fortibble
vsdata.frame
.For example, the function
pb_releases()
do not work whenrenv
is enabled. This is occurring here:piggyback/R/utils.R
Line 69 in 4b7cdb9
With
renv
enabled,remotes[remotes[["name"]] == remote, "url"]
is acharacter
. Hence, using[["url"]]
does not work. Whenrenv
is not enabled, the same is atibble
and can be subsetted using[["url"]]
.I have made an animated GIF that hopefully show the problem clearly. You can see that
pb_releases()
stops working whenrenv
is activated. Whenrenv
is deactivated,pb_releases()
works again.Note that the same problem occurs for some other functions of the packages.
The text was updated successfully, but these errors were encountered: