[00:37:02] <lifeless> dstufft: so, saw a bunch of stuff in 7.0.1
[00:37:37] <lifeless> dstufft: I presume someone hit a fs limit with the cache? That surprised me turning up so quickly :)
[00:51:05] <dstufft> lifeless: hm, don't think so? I don't think 7.0.1 had any fs stuff
[00:51:21] <lifeless> dstufft: you changed the cache path algorithm
[00:51:39] <lifeless> dstufft: the commit says its was a file system limit that drove it
[00:54:52] <dstufft> lifeless: oh, I changed that before 7.0, mostly to use the the hash(full url + "#<hashtype>=<hash>") as the key instead of the filename. Thought about it for awhile and I decided that the risk of people using the same version to mean two different things was big enough compared to the relatively small reward of sharing a cache between two mirrors that have different URLs wasn't worth it
[01:00:11] <lifeless> dstufft: ah. So - FWIW I think that means that e.g. openstack CI will have vey noisy benefits
[01:00:46] <lifeless> dstufft: because they have a local mirror
[01:01:23] <lifeless> dstufft: I would have suggested hashing the artifact as a way to defend against that without giving up on the benfits
[01:01:37] <dstufft> lifeless: we don't have the artifact without downloading it
[01:01:57] <dstufft> lifeless: oh, so my plan btw to handle that is I have some plans to enable better support for multi repositories, and provide a way to override the cache key for that repository
[01:02:11] <dstufft> if you don't say an explicit cache key, it'll use the base url
[01:02:23] <lifeless> dstufft: yeah, but we have the artifact in the cache
[01:02:24] <dstufft> if you do, it'll use that explicit cache key instead of the base url
[01:02:32] <lifeless> dstufft: (or we couldn't have built the cached wheel in the first place)
[01:03:03] <lifeless> dstufft: [and on the second url, we'd only download the artifact, not compile it].