-
Notifications
You must be signed in to change notification settings - Fork 153
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
RemoteSha being added to internally-create packages causing renv::status to fail #2014
Comments
Any chance you can prepare a reproducible example, just so I can investigate more easily? |
Not easily, unfortunately, since it's only happening for private packages on our private PM instance. Do you have a PM instance with git-backed packages that would be publicly accessible? That's the only way I could think of getting closer to something to help me give you more details. If you prefer, I can submit a Posit Support ticket with more detailed logs, but figured I'd start here in case you have thoughts. |
Can you try running the following:
and let me know what output you see? |
I got a bit closer to ~reproducible:
full file (masking our dev URL)
GitLab CI config
For comparison,
Perhaps the issue is actually with |
Sorry for the late response. I think the issue here is actually the differing remote types -- in particular, the second record has:
I've pushed a change in 1c8c64c that might alleviate the issue; please let me know if it makes a difference. |
Thanks for taking a look! I just ran:
Then pushed, and getting a different error trying to install via CI. Any suggestions?
Relevant snippets (lmk if the full files would help):
|
Hmm, I wasn't able to reproduce locally:
Is it possible that your CI system doesn't have access to GitHub for some reason? ( |
hmm looks to be a common issue with More minimal example, running this in CI fails:
I tried using
but, I think it's still failing from Error:
Any suggestions? |
Output of:
Is:
Setting
(seems like a separate bug to investigate, since I wouldn't expect BUT the good news is that I confirmed the latest version of |
Phew, that's awesome to hear. Thanks for confirming! |
Thanks again for making this change in this release! |
I'm finding a subtle regression b/w renv 1.0.7 -> 1.0.10 that I suspect is related to
RemoteSha
changes discussed in #1961.When running in:
renv::status()
shows no issuesrenv::status()
returnsWhen I downgrade to
1.0.7
, thenrenv::snapshot()
removes theRemoteSha
entries for each, which allows the CI to again pass withrenv::status()
showing no issues.Details:
searchr
andmyinternals
(masked names for internal packages) are installed from tag-based git builders on Package Manager.pak
withrenv
.The text was updated successfully, but these errors were encountered: