Closed jennybc closed 3 days ago
I'm going to bring caching back with a bit of modification. Stay tuned.
OK @juliasilge this is done now, complete with restored and upgraded caching. Additional work that is not shown here: I temporarily added lots of logging to verify that the cache was being used/updated as expected and I was satisfied with the results.
I have already rebased and force pushed this PR branch to include the ark version bump I did earlier today. Do you need to refetch this branch? Any chance you've got a local ark build that's getting used in the dev build instead of the 0.1.154 release from this afternoon?
I just re-did the QA step described above and I'm still getting the desired pop-up, with locally built ark and after doing cargo clean
forcing an ark release download:
I think it's possible what we need is step 4 here, like this commit.
🤔 step 4 has happened, in main
, in 34695a1276d865021bc4ffaac5a0746615956341. And this PR is rebased on that.
Here's the ark requirement in positron/extensions/positron-r/package.json
in this branch:
It does feel like an ark mismatch. Does .ps.ark.version()
report 0.1.154 in your dev build?
I made one more change, but it would not explain what you're seeing (a complete lack of prompt).
Addresses #1957
Requires https://github.com/posit-dev/ark/pull/625
What's the payoff?
QA Notes
To experience that
checkInstalled()
still works and to see the user-facing message in the absence of a minimum version requirement, here's one idea:remove.packages("styler")
You should see this:
To experience that
checkInstalled()
still works and to see the user-facing message in the presence of a minimum version requirement, here's one idea:pak::pak("renv@1.0.8")
.Walk through File > New Project > R Project and click the box to use renv:
As the new project is being stood up, you should see this: