From: "Michael T. Richter" Date: 2008-06-02T15:12:23+09:00 Subject: Re: Gems not working --=-iB868cVIS3mjzc5SipQ+ Content-Type: multipart/alternative; boundary="=-+RHnB7MvqzKQSYGArkqn" --=-+RHnB7MvqzKQSYGArkqn Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-06-02 at 10:31 +0900, Tom Copeland wrote: > What surprises me is seeing the gem client fetch the uncompressed index > (that is, the yaml file) rather than fetching the compressed index. The > compressed version is only 1MB, and seems like that would be much less > likely to time out. It might be worth posting to the > rubygems-developers list and seeing if they could help you hunt down > this problem. There's a lot that surprises me in the recent gem releases (1.0+). The fact that there seems to be absolutely no caching of metadata is the first point of surprise. Even if I tell it NOT to go looking for the metadata it goes looking for the metadata which indicates to me that it's not caching locally at all and has to. Then the fact, as you point out, that it needs to download the whole YAML file instead of the compressed version is suspicious. I'm seriously unimpressed with the 1.0+ versions of gem, frankly. And yet another mailing list to sign up for? God DAMN! How about just a bug tracker somewhere? Is there an URL for that? I really don't want to increase my incoming mail any more than I already have it. :( --=20 Michael T. Richter (GoogleTalk: ttmrichter@gmail.com) We should sell bloat credits, the way the government sells pollution credits. Everybody's assigned a certain amount of bloat, and if they go over, they have to purchase bloat credits from some other group that's been more careful. (Bent Hagemark) --=-+RHnB7MvqzKQSYGArkqn Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Mon, 2008-06-02 at 10:31 +0900, Tom Copeland wrote: 
What surprises me is seeing the gem client fetch th=
e uncompressed index
(that is, the yaml file) rather than fetching the c=
ompressed index.  The
compressed version is only 1MB, and seems like that=
 would be much less
likely to time out.   It might be worth posting to =
the
rubygems-developers list and seeing if they could h=
elp you hunt down
this problem.

There's a lot that surprises me in the recent gem releases (1.0+).  Th= e fact that there seems to be absolutely no caching of metadata is the firs= t point of surprise.  Even if I tell it NOT to go looking for the meta= data it goes looking for the metadata which indicates to me that it's not c= aching locally at all and has to.  Then the fact, as you point out, th= at it needs to download the whole YAML file instead of the compressed versi= on is suspicious.  I'm seriously unimpressed with the 1.0+ versions of= gem, frankly.

And yet another mailing list to sign up for?  God DAMN!  How abou= t just a bug tracker somewhere?  Is there an URL for that?  I rea= lly don't want to increase my incoming mail any more than I already have it= .  :(

--
Michael T. Richter <ttmri= chter@gmail.com> (GoogleTalk: ttmrichter@gmail.com)
We should sell bloat credits, the way the government sells pollution cre= dits. Everybody's assigned a certain amount of bloat, and if they go over, = they have to purchase bloat credits from some other group that's been more = careful. (Bent Hagemark)
--=-+RHnB7MvqzKQSYGArkqn-- --=-iB868cVIS3mjzc5SipQ+ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIQ49dLqyWkKVQ54QRAkx1AJ9XDxRmr/pgD4cJFCp2Y17WEjxjsACgxgic XP/313oNGFkpuMBYH0zm0B0= =8kVH -----END PGP SIGNATURE----- --=-iB868cVIS3mjzc5SipQ+--