rubytorrent devel - Feb 2005 - Regarding '' info'' Bug

I think i tracked down the situation.

Using RubyTorrent::BitTorrent.new
with only a single argument of metainfo leads to a Package being  
created from ''metainfo.info'',
and then Package internally calls info again, dieing.

invoking like
bt =  
RubyTorrent::BitTorrent.new(dtorrent.metainfo,RubyTorrent:: 
Package.new(dtorrent.metainfo))
avoids this, but then a new problem is discovered.  Unless another  
argument is passed after the
Package there will be an exception as args (in BitTorrent.iniitalize)  
will be nil.

So calling it like
RubyTorrent::BitTorrent.new(dtorrent.metainfo,RubyTorrent:: 
Package.new(dtorrent.metainfo),:ulratelim => 5*1024)
with some any argument that get_args would like, will avoid this.

I''m not sure about the intended behavior, but i thought i would pass  
this along. It now seems that i have
the Torrent Client connecting to the aversa tracker''s announce.. at  
least it is making a GET request, whether
it is properly registered is a whole other story =p..

Thanks!

Excerpts from Curtis Schofield''s mail of  7 Feb 2005
(EST):
> I think i tracked down the situation.
Thanks for the bug reports. They were due to some small silliness on my
part. I''ve fixed these problems in CVS. Please try it and let me know
if
you have any more problems.

-- 
William <wmorgan-rubytorrent-devel@masanjin.net>