[mnet-devel] debugging _new's relay client behavior

[Zooko]

I got this in my v0.6.1 relay server:

2003-03-03_04:57:41 (conversation) <=== <trnn9>: receiving: "(id: <nryfo>, type: are there messages, body: {'mojo header':{'mojo offer':0}, 'mojo message':None})", 1525 bytes uncomp
2003-03-03_04:57:41 (conversation) _process(): BadFormatError in message from <trnn9>, msg: '(4:dict(6:string6:header)(4:dict(6:string12:message type)(6:string18:are there messages)(6:string5:nonce)(6:string20:[>[\x12j\x91\x92\xd8<nJq\xf7\xf25A\xf5\xc3p))(6:string8:protocol)(6:string12:Moj...Ss9uk_H4I1k)))))(6:string8:platform)(6:string6:linux2)(6:string5:pyver)(6:string76:2.2.2 (#1, Dec  5 2002, 15:48:42) \n[GCC 2.95.4 20011002 (Debian prerelease)])(6:string12:sequence num)(3:int1:3)))', error: <BadFormatError: ({'header':{'message type':'are there messages', 'nonce':<mc9fs>, 'protocol':'Mojo v0.9991', 'recipient':<dy3zi>}, 'message body':{'mojo header':{'mojo offer':0}, 'mojo message':None}, 'metainfo':{'broker version':None, 'connection strategies':[{'broker id':<trnn9>, 'comm strat sequence num':1, 'comm strategy type':'crypto', 'lowerstrategy':{'broker id':<trnn9>, 'comm strat sequence num':1, 'comm strategy type':'relay', 'relayer id':<dy3zi>}, 'pubkey':{'key header':{'cryptosystem':'RSA', 'type':'public', 'usage':'only for communication security'}, 'key values':{'public exponent':'3', 'public modulus':'2EGu887zW85XXUS6o6KGApbLKYY1m0wdN-wXRDLGDdZ1mWmBrUiUOvezcOwCDhd25Sy8ej6ClhUHbrbccpdbcxZ40HHKAqdsV9kvEQ5Cku6h8KjdV46OZZ9R_Vfgy6RndjL_aUuA1zrXx-FuQqix14bLNzldoNK-Ss9uk_H4I1k'}}}], 'platform':'linux2', 'pyver':'2.2.2 (#1, Dec  5 2002, 15:48:42) \n[GCC 2.95.4 20011002 (Debian prerelease)]', 'sequence num':3}}, None, <BadFormatError: "failed template check because: (mismatch in key ('mojo message'): target is not a dict) template was: ({'mojo message':OptionMarker: <{'response version':OptionMarker: <1>}>}) target was: ({'mojo header':{'mojo offer':0}, 'mojo message':None})">)>


Compare to an "are there messages" from a v0.6.1 client:

2003-03-03_04:55:58 (conversation) <=== <ie7bh>: receiving: "(id: <aca5d>, type: are there messages v2, msg: {'response version':3})", 473 bytes uncomp


It isn't the "v2" -- my v0.6.1 RS handles that fine, it's the presence of "mojo 
header", "mojo message" in the message.  Both of those fields exist in the 
messages sent by v0.6.1 clients, but they are not included in body.  I suspect 
that _new might be sending something like:

{'mojo header': {'mojo offer': 0}, 'mojo message': {'mojo header': {'mojo offer': 0}, 'mojo message': None}}

where v0.6.1 sends:

{'mojo header': {'mojo offer': 0}, 'mojo message': None}

I've updated my RS to print out more detailed debugprints on BadFormatError...

--Z



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel