I think I've just seen an edge case using our local CRAN repo.
Essentially we're trying to use some CI and we're trying to use a structure similar to the https://github.com/sol-eng/bike_predict sample.
Because of this we often see these things happen very close in time together:
- package builds and deploys (including version increments) in our CRAN
- manifest.json updates picked up in RStudio Connect
During one update today this caused an error during RStudio Connect git shiny app update of:
curl: HTTP 404 https://cran.mycorp.app/src/contrib/ourPackage_0.2.3.tar.gz
which was caused by the fact that ourPackage_0.2.3.tar.gz had (during the 10 or so minutes that RStudio Connect was taking to build packages) been replaced by ourPackage_0.2.4.tar.gz (0.2.3 was now in the archive on the cran server)
We are looking at sorting out some of our CI versioning pain anyway here...
but I'm also wondering if we can somehow get RStudio Connect to fallback to looking in https://cran.mycorp.app/src/contrib/Archive/ if a 404 occurs in the contrib folder?