Preset package caching sometimes unreliable
Appears sometimes the package cache doesn't validate correctly causing an out of date package to be cached and not updated until cache is purged. Maybe due to the present cache showing as up to date, but it's actually not due to some sort of packaging error. Needs further investigation.
Updated by krileon about 1 year ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
This appears to be due to the bundle caching using the filename of the preset. It should in fact always be using the download id. The download id is a md5 of every package id and the version of the package being downloaded. This guarantees it's always unique to what is being download for complete accuracy of the cache. The filename is now entirely cosmetic as it should've been.