GitHub Gem Server Slow Updating Metadata, Frequent 404s
Reported by Alex Coles | May 7th, 2008 @ 03:45 AM
I added http://gems.github.com/ to my source list. I am experiencing a real slow down in using the gem command since.
I may be having some network latency/DNS issues, but I've still noticed a correlation between adding http://gems.github.com/ and before.
Additionally, I don't know if there is a way to work around the frequent 404 output: see http://pastie.caboo.se/192919.
Comments and changes to this ticket
-
defunkt May 9th, 2008 @ 05:05 PM
- → Assigned user changed from “defunkt” to “PJ Hyett”
-
Mislav May 10th, 2008 @ 05:58 AM
I've also noticed this and think that is a bug with rubygems. IMO, it doesn't handle multiple sources well (specifically, caching of metadata from sources other than rubyforge).
I've also noticed 404s, but I don't think this is related (you should file a separate bug report for that)
-
PJ Hyett May 14th, 2008 @ 09:35 PM
- → State changed from “new” to “hold”
We don't recommend adding gems.github.com to sources anymore due to these issues. Unfortunately, we don't have a fix yet, but we're aware of the problem.
-
Jeremy June 18th, 2008 @ 07:21 AM
Any update on this? Ran two separate installs in a 15 min period of time and it had to update the metadata for all 518 gems both times. Takes what seems to be a long time. Only to find out that the gem (evanphx-gemjour) was not available.
-
PJ Hyett June 18th, 2008 @ 02:24 PM
- → Milestone cleared.
Fortunately, yes, there is a new release of RubyGems coming soon that fixes not only multiple sources, but also the slow metadata issue.
Hang tight!
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
