tag:help.rubygems.org,2010-01-19:/discussions/problems/22577-yard-cachingRubyGems.org: Discussion 2018-10-18T19:51:29Ztag:help.rubygems.org,2010-01-19:Comment/405776162016-08-20T14:04:32Z2016-08-20T14:04:32ZYARD Caching<div><p>We don't run rubydoc actually so we don't have access to do
that. Sorry!</p></div>Evan Phoenixtag:help.rubygems.org,2010-01-19:Comment/405776162016-08-20T14:56:35Z2016-08-20T14:56:36ZYARD Caching<div><p>It's happened before though and it appeared to be sorted by one
of the support staff. See PREVIOUSLY below.<br>
Is it possible that the server cache just expired naturally?</p>
<p>PREVIOUSLY<br>
On Wednesday, 22 June 2016:<br>
From: lsegal (Support staff)</p>
<p>Looks like it was a cache issue. Should be resolved now!</p>
<p>On Wed, Jun 22 at 09:19 AM PDT, wrote:</p>
<p><a href="http://www.rubydoc.info/gems/puree/0.15.0">http://www.rubydoc.info/gems/puree/0.15.0</a></p>
<p>Half of the docs are showing up as those of the previous version
0.14.0, which must be very confusing for anybody coming across
them.</p>
<p>This is also the case when the frames option is used<br>
<a href="http://www.rubydoc.info/gems/puree/frames">http://www.rubydoc.info/gems/puree/frames</a></p></div>Adrian Albin-Clarktag:help.rubygems.org,2010-01-19:Comment/405776162016-08-20T15:10:40Z2016-08-20T15:10:42ZYARD Caching<div><p>Sorry, I've already realised that it was the rubydoc guys that I
contacted before and not yourselves. Silly me.</p></div>Adrian Albin-Clark