Home → Problems →

Yard documentation generation... again?

• Edit

ronen barzel

09 Apr, 2011 03:00 PM

Hi, I'm seeing what looks like the same issue as in this recently-closed discussion:

https://rubydoc.tenderapp.com/discussions/problems/26-yard-documentation-generation

That is, I pushed a new gem to rubygems.org about six hours ago, but the docs haven't yet(?) shown up:

http://rubydoc.info/gems/array_floe/1.0.0/frames

That previous discussion said that the docs get pulled every hour, so i wonder where there may be another cron problem rearing its head? Though I'm new at this, so could there be pilot error on my part?

Thanks

1. Support Staff 1 Posted by lsegal on 09 Apr, 2011 05:55 PM

   

   Actually in this case it's not our fault, but RubyGems' list. Although we update once an hour, RG doesn't always update its list hourly:

   $ irb
   >> Gem::SpecFetcher.fetcher.list(true).values.first.select {|x| x[0] =~ /^array_/ }
   => [["array_metrics", #<Gem::Version "0.0.1">, "ruby"], ["array_metrics", 
         #<Gem::Version "0.0.2">, "ruby"], ["array_pair", #<Gem::Version "0.0.1">,
         "ruby"], ["array_pair", #<Gem::Version "0.1.0">, "ruby"], ["array_partition",
         #<Gem::Version "0.1.0">, "ruby"], ["array_statistics", #<Gem::Version "0.1.0">,
         "ruby"], ["array_stats", #<Gem::Version "0.6.0">, "ruby"]]
   

   • Edit

2. 2 Posted by ronen barzel on 09 Apr, 2011 09:31 PM

   

   Aha -- I didn't suspect that, since RG already had the homepage for the gem up. As it turns out, between the time of your response and now, RG's list has been updated so it seems things are working on the RG side, if not as quickly. And the gem has been picked up by rubydoc.info.

   Thanks for your quick reply. And for providing and maintaining this service!

   • Edit

3. Support Staff 3 Posted by lsegal on 09 Apr, 2011 09:39 PM

   

   No problem.

   AFAIK, the "slow update" only occurs on newly registered gems. Updated versions of gems tend to get updated quite fast on their lists (within the hour), so you should be fine from now on.

   • Edit

4. lsegal closed this discussion on 09 Apr, 2011 09:39 PM.