tag:help.rubygems.org,2010-01-19:/discussions/problems/502-internal-server-error-when-trying-to-login-or-push-a-gemRubyGems.org: Discussion 2011-04-07T20:59:37Ztag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T07:51:45Z2011-02-27T07:51:45ZInternal server error when trying to login or push a gem<div><p>What's your gemspec? Trying to debug this issue, I'm seeing
successful gem pushes in the past few hours.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T08:42:14Z2011-02-27T08:42:15ZInternal server error when trying to login or push a gem<div><p>I'm having exactly the same problem. Searching 'rubygems' on
twitter shows we're not alone either.</p>
<p>eg:</p>
<p>% rake release<br>
(in /home/clive/Repositories/git/DarkArtsStudios/yaml-model)
yaml-model 1.3.5 built to pkg/yaml-model-1.3.5.gem<br>
Tagged v1.3.5<br>
Pushed git commits and tags<br>
Untagged v1.3.5 due to error<br>
rake aborted!<br>
Pushing gem to RubyGems.org...<br></p>
<h1>Internal Server Error</h1>
<p>(See full trace by running task with --trace)</p></div>Clive Croustag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T08:44:48Z2011-02-27T08:44:49ZInternal server error when trying to login or push a gem<div><p>Same as above, but commands called in a codeblock (sorry)</p>
<pre>
<code>% rake release
(in /home/clive/Repositories/git/DarkArtsStudios/yaml-model)
yaml-model 1.3.5 built to pkg/yaml-model-1.3.5.gem
Tagged v1.3.5
Pushed git commits and tags
Untagged v1.3.5 due to error
rake aborted!
Pushing gem to RubyGems.org...
<h1>Internal Server Error</h1>
(See full trace by running task with --trace)</code>
</pre></div>Clive Croustag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T08:48:25Z2011-02-27T08:48:26ZInternal server error when trying to login or push a gem<div><p>And here's using gem directly:</p>
<pre>
<code>% gem push --verbose pkg/yaml-model-1.3.5.gem
Pushing gem to RubyGems.org...
POST https://rubygems.org/api/v1/gems
500 Internal Server Error
<h1>Internal Server Error</h1></code>
</pre></div>Clive Croustag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T09:21:07Z2011-02-27T09:21:08ZInternal server error when trying to login or push a gem<div><p>Same problem here. Could push yesterday with the same gemspec,
added homepage information today, but cannot push even if I remove
it.<br></p>
<hr>
<p>Gemspec is:</p>
<pre>
<code># -*- encoding: utf-8 -*-
$:.push File.expand_path("../lib", __FILE__)
require "micro-optparse/version"
Gem::Specification.new do |s|
s.name = "micro-optparse"
s.version = Micro::Optparse::VERSION
s.platform = Gem::Platform::RUBY
s.authors = ["Florian Pilz"]
s.email = ["fpilz87@googlemail.com"]
s.homepage = "http://florianpilz.github.com/micro-optparse/"
s.summary = %q{A very small wrapper around optparse.}
s.description = %q{This gem wraps all the functionality of optparse into an easy to use, clear and short syntax. In addtion, strong validations are added. You can either use this gem as a lightweight alternative to trollop or copy all its 75 lines into your script to have an command-line parser without injecting a gem dependency.}
s.license = "MIT"
s.files = `git ls-files`.split("\n")
s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
s.require_paths = ["lib"]
end</code>
</pre></div>Florian Pilztag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T10:42:26Z2011-02-27T10:42:29ZInternal server error when trying to login or push a gem<div><p>Works now - for me at least. :) Thank you!</p></div>Florian Pilztag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T12:51:52Z2011-02-27T12:51:53ZInternal server error when trying to login or push a gem<div><p>Yep, looks fine to me now as well. Cheers!</p></div>stephen hardistytag:help.rubygems.org,2010-01-19:Comment/56087162011-02-27T18:31:34Z2011-02-27T18:31:34ZInternal server error when trying to login or push a gem<div><p>Sorry about the problems here, folks. Closing this one out.</p></div>Nick Quaranto