Fail behavior

[Scott Chamberlain]

E.g., for packages that don't exist:

http://cranlogs.r-pkg.org/downloads/total/last-day/doesnotexist

[
  {
      start: "2015-07-07",
      end: "2015-07-07",
      downloads: 0,
      package: "doesnotexist"
  }
]

I would think a pkg that's not found would give a 404 - of course I know that package doesn't exist, but a machine doesn't know

[Gábor Csárdi]

Currently I cannot tell if a package does not exist, or just was not downloaded. For this I would need to cross-reference the crandb JSON db. Certainly possible, but somewhat cumbersome, so I haven't done it yet.

[Scott Chamberlain]

Okay, makes sense, thanks again

[Gábor Csárdi]

Note for myself. This could be implemented by getting the list of packages (active + archived) from crandb periodically, e.g. once a day, storing it in (say) Redis, and using that as a baseline.