GitHub is aggressively caching raw.github, breaking many use cases
1–10 of 145 posts
Re: GitHub is aggressively caching raw.github, breaking many use cases
#2Not asking this to distract from the problem but can you link to the raw version of a specific commit/ref?
Re: GitHub is aggressively caching raw.github, breaking many use cases
#3There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.
Re: GitHub is aggressively caching raw.github, breaking many use cases
#4Not asking this to distract from the problem but can you link to the raw version of a specific commit/ref?
Re: GitHub is aggressively caching raw.github, breaking many use cases
#5There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.
[deleted]
Re: GitHub is aggressively caching raw.github, breaking many use cases
#6[flagged]
Re: GitHub is aggressively caching raw.github, breaking many use cases
#7There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.
You can eliminate the cache invalidation problem by not reusing old names for new things.
Re: GitHub is aggressively caching raw.github, breaking many use cases
#8[flagged]
Has github fired most people capable of fixing problems?
Re: GitHub is aggressively caching raw.github, breaking many use cases
#9Reading the comment threads on GitHub, some files get a TTL of 300, some get a TTL of 86400. The "why" is certainly an interesting question.