Home → Problems →

500 Internal Server Error when pushing a gem

• Edit

Conor

09 Nov, 2017 08:17 PM

Hi,

I'm trying to push a new gem to RubyGems this afternoon and am getting a 500 internal server error. Here is the verbose output:

$ gem push --verbose fanciful-0.0.1.gem
GET https://api.rubygems.org/latest_specs.4.8.gz
304 Not Modified
Pushing gem to https://rubygems.org...
POST https://rubygems.org/api/v1/gems
500 Internal Server Error
There was a problem saving your gem. Please try again.

and the debug output

$ gem push --debug -V fanciful-0.0.1.gem
NOTE: Debugging mode prints all exceptions even when rescued
Exception `LoadError' at /Users/landry/.rbenv/versions/2.4.0/lib/ruby/2.4.0/resolv.rb:171 - LoadError
Exception `Errno::EEXIST' at /Users/landry/.rbenv/versions/2.4.0/lib/ruby/2.4.0/fileutils.rb:228 - File exists @ dir_s_mkdir - /Users/landry/.gem/specs/api.rubygems.org%443
GET https://api.rubygems.org/latest_specs.4.8.gz
304 Not Modified
Pushing gem to https://rubygems.org...
POST https://rubygems.org/api/v1/gems
500 Internal Server Error
There was a problem saving your gem. Please try again.

Is something going on with the server? https://status.rubygems.org/ is 'All Systems Operational`

1. 1 Posted by Conor on 09 Nov, 2017 09:17 PM

   

   I found the problem. I had gem.date set to '1017-11-09' instead of '2017-11-09'. It works now. Should the server be giving a 500 error when this happens or is this a bug in rubygems?

   • Edit

2. Support Staff 2 Posted by David Radcliffe on 09 Nov, 2017 09:18 PM

   

   I saw this error on the server. It was unable to parse the data. We probably should be returning a 4xx error since this was bad input.

   • Edit