Subject: Re: gem server problems in 0.9.5 - msg#00025

Previous Message by Date: click to view message preview

Re: RubyGems 1.0 release soon

On Dec 15, 2007 8:35 PM, Eric Hodel <drbrain-48TerJ1FxhPk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> wrote: > Are there any other outstanding issues or important bugs that should > be fixed in the tracker? Or bugs that didn't make it into the tracker? I am still having problems with gem server in 0.9.5. I just updated that thread with my debug output. This seems like a problem, because I am not doing anything different than 0.9.4, and it won't serve my local test gems anymore. I'd be glad to help resolve this (or understand what I'm doing wrong and why it's not a problem). I'll keep debugging trying to see what is different from 0.9.4, and update the thread with what I find. I don't have a ticket for this yet, but I can create one if you want... -- Chad

Next Message by Date: click to view message preview

Question on GEM_PATH

When I use GEM_PATH to add an additional local repository to be used, what dirs must be in that repository? gems? specifications? docs? cache? others? Also, a related question. If I have a source checkout of a gem locally, can I somehow put it on my GEM_PATH to be loaded, even if it doesn't follow the standard repository layout? The use case would be to perform updates on a dependency gem, and have those updates immediately usable by a separate local app, without having to actually do the step to build and install the gem to a local repository. Thanks, Chad

Previous Message by Thread: click to view message preview

Re: gem server problems in 0.9.5

Here is a trace from ruby-debug, right before I get the exception. On Dec 13, 2007 3:43 PM, Eric Hodel <drbrain-48TerJ1FxhPk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> wrote: > On Dec 13, 2007, at 13:37 PM, Eric Hodel wrote: > > On Dec 11, 2007, at 24:30 AM, Chad Woolley wrote: > >> > >> Is this a bug, or am I doing something wrong? > > > > You certainly shouldn't get 500s. I'll look into it, but if you can > > run with --debug it might give a backtrace. > > Fixed. > This is still a problem with the trunk as of right now. Here is my ruby-debug session, which shows the stack right before I get the exception. It gets into fetch_single_spec, then blows up looking for a /quick/Marshal...rz file: chadmac:~ woolley$ rm -rf ~/.gem; rdebug /usr/local/bin/gem -- list --remote --source=http://127.0.0.1:9909 /usr/local/bin/gem:8 require 'rubygems' [3, 12] in /usr/local/bin/gem 3 # Copyright 2006 by Chad Fowler, Rich Kilmer, Jim Weirich and others. 4 # All rights reserved. 5 # See LICENSE.txt for permissions. 6 #++ 7 => 8 require 'rubygems' 9 require 'rubygems/gem_runner' 10 11 required_version = Gem::Requirement.new ">= 1.8.2" 12 (rdb:1) b /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:397 Set breakpoint 1 at /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:397 (rdb:1) c *** REMOTE GEMS *** Updating metadata for 8 gems from http://127.0.0.1:9909 Breakpoint 1 at /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:397 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:397 marshal_uri = source_uri + "/quick/Marshal.#{Gem.marshal_version}/#{spec_name}.gemspec.rz" [392, 401] in /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb 392 393 # Tries to fetch Marshal representation first, then YAML 394 def fetch_single_spec(source_uri, spec_name) 395 @fetch_error = nil 396 begin => 397 marshal_uri = source_uri + "/quick/Marshal.#{Gem.marshal_version}/#{spec_name}.gemspec.rz" 398 zipped = fetcher.fetch_path marshal_uri 399 return Marshal.load(unzip(zipped)) 400 rescue => ex 401 @fetch_error = ex (rdb:1) where --> #0 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:397 in 'fetch_single_spec' #1 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:425 in 'update_with_missing' #2 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:424 in 'update_with_missing' #3 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:293 in 'update' #4 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_info_cache_entry.rb:33 in 'refresh' #5 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_info_cache.rb:135 in 'refresh' #6 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_info_cache.rb:128 in 'refresh' #7 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_info_cache.rb:40 in 'cache' #8 /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_info_cache.rb:50 in 'search' #9 /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/query_command.rb:52 in 'execute' #10 /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/list_command.rb:31 in 'execute' #11 /usr/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:136 in 'invoke' #12 /usr/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:104 in 'process_args' #13 /usr/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:74 in 'run' #14 /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:39 in 'run' #15 /usr/local/bin/gem:22 in 'new'

Next Message by Thread: click to view message preview

Re: gem server problems in 0.9.5

On Dec 15, 2007, at 21:39 PM, Chad Woolley wrote: > On Dec 13, 2007 3:43 PM, Eric Hodel > <drbrain-48TerJ1FxhPk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> wrote: >> On Dec 13, 2007, at 13:37 PM, Eric Hodel wrote: >>> On Dec 11, 2007, at 24:30 AM, Chad Woolley wrote: >>>> >>>> Is this a bug, or am I doing something wrong? >>> >>> You certainly shouldn't get 500s. I'll look into it, but if you can >>> run with --debug it might give a backtrace. >> >> Fixed. > > This is still a problem with the trunk as of right now. Here is my > ruby-debug session, which shows the stack right before I get the > exception. It gets into fetch_single_spec, then blows up looking for > a /quick/Marshal...rz file: > > [...] Can you give me a log of it running without the debug stuff? I need to know what's coming back from the server. Also, your test gems may be useful in tracking this down. I added some code that'll make RubyGems give a little more information when retrieval of files raises an error. Be sure to have revision 1550 or newer. For what it's worth, I'm not having any problems with `gem server` out of trunk: $ sudo ruby -Ilib bin/gem sources --clear Password: *** Removed user source cache *** *** Removed system source cache *** $ rm -r ~/tmp/gems $ ruby -Ilib bin/gem install -i ~/tmp/gems --source http://localhost:8808 ruby2ruby Updating metadata for 16 gems from http://localhost:8808 ................ complete Successfully installed rubyforge-0.4.4 Successfully installed rake-0.7.3 Successfully installed hoe-1.3.0 Successfully installed RubyInline-3.6.5 Successfully installed ParseTree-2.0.2 Successfully installed ruby2ruby-1.1.7 6 gems installed [ri/rdoc installation follows] I was also successful installing using 0.9.4, minus a few bugs that are present in 0.9.4. The server was run as: $ ruby -Ilib bin/gem server Starting gem server on http://localhost:8808/ [GET/HEAD requests, all 200]