`repo_resolve()` cuts out after `2023-02-14`

[maxheld83]

trafficstars

I've run into some puzzling behavior:

(For reproducibility, I used the rig image)

docker run -it ghcr.io/r-lib/rig/ubuntu-22.04-release R --no-save 

pak::repo_resolve("PPM@2023-02-14")
# CRAN 
# "https://packagemanager.posit.co/cran/16710885"
pak::repo_resolve("PPM@2023-02-15")
# CRAN 
# "https://packagemanager.posit.co/cran/0"

odder still, afterwards, any requests give the same response:

pak::repo_resolve("PPM@2023-02-14")
# CRAN 
# "https://packagemanager.posit.co/cran/0"

It seems that at this point, pak is stuck, and the only way to get it produce any pak::repo_resolve()s again is to shut down the image (or all running R processes, if reproducing on the host).

I've verified that there are PPM builds for 2023-02-15 (see here).

Many later dates also seem to fail, though I haven't tried them all.

I've reproduced the issue:

• with devel and stable (above is pak 0.7.2.9000)
• ubuntu 22 (on the host and above image)
• macos

This also filters up to pak::repo_add() etc.

[gaborcsardi]

I think this is probably the same as https://github.com/r-lib/pkgcache/issues/110