Re: installing gems from gemcutter not as it should be
It's working for me... % gem fetch RedCloth -Vv 4.2.0 GET 200 OK: http://gemcutter.org/specs.4.8.gz Downloading gem RedCloth-4.2.0.gem GET 302 Moved Temporarily: http://gemcutter.org/gems/RedCloth-4.2.0.gem GET 200 OK: http://s3.amazonaws.com/gemcutter_production/gems/RedCloth-4.2.0.gem Downloaded RedCloth-4.2.0 Perhaps it was a temporary fluke? Does it work now? -Nick On Thu, Oct 29, 2009 at 9:55 AM, markdevilliers markdevilli...@gmail.comwrote: Hey Guys - not too sure if I should post this here but I keep getting the following type errors - Heroku receiving push - Installing gem right_aws 1.10.0 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed right_http_connection-1.2.4 Successfully installed right_aws-1.10.0 2 gems installed - Installing gem right_http_connection 1.2.4 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed right_http_connection-1.2.4 1 gem installed - Installing gem populator 0.2.5 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed populator-0.2.5 1 gem installed - Installing gem faker 0.3.1 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed faker-0.3.1 1 gem installed - Installing gem RedCloth 4.2.0 from http://gemcutter.org, http://gems.rubyforge.org ERROR: http://gemcutter.org/ does not appear to be a repository ERROR: could not find gem RedCloth locally or in a repository error: hooks/pre-receive exited with error code 1 To me it looks like maybe more from the gemcutter side than the heroku side but it is stopping me from deploying as is. Annoyingly it did work earlier on in the day By the way is this the best way to contact you guys if we are having service problems? Thanks, Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: installing gems from gemcutter not as it should be
It did work for me a couple of hours later. It had also failed several times before I posted. I think the issue is consistency - random gems (not always redcloth) were failing to install with the error message - http:// gemcutter.org/ does not appear to be a repository - which in the example above doesn't make sense as it was a repository moments before. I'll probably accept that maybe gemcutter is a bit overloaded a certain times and timing out delivering the initial 302 but maybe on the heroku side there needs to be a try a few times on push as failing at random stages is a bit annoying. Anyway I've just pushed again and all is good again, Thanks for looking into it for me - Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: installing gems from gemcutter not as it should be
Just a thought. Are the requests to gemcutter using HTTP? Is the system using ETags / If-Mod-since? Seems there could be a way to use a forward proxy to gemcutter. It would help out: 1) less bandwidth for both gemcutter and heroku 2) faster image build times on heroku 3) less load on the gemcutter servers 4) maybe less load on the heroku servers since Another option would be to have a local repository of gems. I remember doing this with rpms/gentoo ports. It was a bit of a pain but as the number of machines increased, it really sped things up. (Especially when installing the software) --Keenan On Nov 2, 2009, at 11:51 AM, Neil Middleton wrote: I had this same problem last week - in the end, and on about the tenth push it finally managed to make it through which was a real pita. Something needs to be there to ensure deployments aren't killedwhatever that might be. /Neil On 2 Nov 2009, at 16:46, markdevilliers wrote: It did work for me a couple of hours later. It had also failed several times before I posted. I think the issue is consistency - random gems (not always redcloth) were failing to install with the error message - http:// gemcutter.org/ does not appear to be a repository - which in the example above doesn't make sense as it was a repository moments before. I'll probably accept that maybe gemcutter is a bit overloaded a certain times and timing out delivering the initial 302 but maybe on the heroku side there needs to be a try a few times on push as failing at random stages is a bit annoying. Anyway I've just pushed again and all is good again, Thanks for looking into it for me - Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: installing gems from gemcutter not as it should be
Yes, we are. http://github.com/qrush/gemcutter/blob/master/app/metal/hostess.rb#L13-34 -Nick On Mon, Nov 2, 2009 at 1:17 PM, Keenan Brock kee...@thebrocks.net wrote: Just a thought. Are the requests to gemcutter using HTTP? Is the system using ETags / If-Mod-since? Seems there could be a way to use a forward proxy to gemcutter. It would help out: 1) less bandwidth for both gemcutter and heroku 2) faster image build times on heroku 3) less load on the gemcutter servers 4) maybe less load on the heroku servers since Another option would be to have a local repository of gems. I remember doing this with rpms/gentoo ports. It was a bit of a pain but as the number of machines increased, it really sped things up. (Especially when installing the software) --Keenan On Nov 2, 2009, at 11:51 AM, Neil Middleton wrote: I had this same problem last week - in the end, and on about the tenth push it finally managed to make it through which was a real pita. Something needs to be there to ensure deployments aren't killedwhatever that might be. /Neil On 2 Nov 2009, at 16:46, markdevilliers wrote: It did work for me a couple of hours later. It had also failed several times before I posted. I think the issue is consistency - random gems (not always redcloth) were failing to install with the error message - http:// gemcutter.org/ does not appear to be a repository - which in the example above doesn't make sense as it was a repository moments before. I'll probably accept that maybe gemcutter is a bit overloaded a certain times and timing out delivering the initial 302 but maybe on the heroku side there needs to be a try a few times on push as failing at random stages is a bit annoying. Anyway I've just pushed again and all is good again, Thanks for looking into it for me - Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
