[7422] in testers

home help back first fref pref prev next nref lref last post

Re: jwgc issues

daemon@ATHENA.MIT.EDU (Greg Hudson)
Sat Mar 25 11:50:27 2006

Date: Sat, 25 Mar 2006 11:49:57 -0500
Message-Id: <200603251649.k2PGnvsG028549@egyptian-gods.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
CC: testers@MIT.EDU
In-reply-to: <200603222114.k2MLELC5019287@egyptian-gods.mit.edu>

Okay, all of these should be fixed.  A few notes for the curious:

> jwgc also fails to update its internal roster representation when
> you "jctl subscribe" to your own presence, for much the same reason.
> I did find the server code which makes that decision, though again,
> no clause in RFC 3921 to suggest that it's correct.

I was wrong; you do get roster pushes when you add yourself to your
roster.  jwgc just mostly ignored roster pushes.

> I still need to look into this one more.  "jctl show" seems broken
> in general.

I wound up just taking the patch for this one.

> 3. [7416] Crash sending to "username"

I also noticed that "jwrite yourself" is supposed to actually work, by
virtue of a partial match on your own JID, but there was a second bug
there.  I fixed that.

A third bug is that the partial matcher is too aggressive; "foo" will
match "foobar@mit.edu".  I didn't fix that for now, but it may come up
as an issue later.

> 4. [7417] Authentication/connection failures handled poorly

This turned out to be easier than I thought.  I simply took away the
retry state for auth errors, and made jwgc display a message and exit
instead.


home help back first fref pref prev next nref lref last post