failed renv update causing diagnostics system to break

I was updating an renv lockfile within a project with new versions of packages; the entirety of the tidyverse had to install, so this was taking an entire workday. Unfortunately, while I was in a meeting away from my computer, it had fallen asleep and so the installation terminated. Frustrated that I had essentially lost an entire days worth of coding work for nothing, I have since ignored the use of the project altogether and have just been using the naked script, which has been working fine for me. Except for the fact that my code has since been running incredibly slow, which was only resolved by turning off diagnostics as seen in this post here , which perfectly described my symptoms and the solution worked as well.

Is there anyway to still use the diagnostics in RStudio and have acceptable execution speeds?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.