Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#23 closed defect (fixed)

improve LOCAL method-failed error message

Reported by: Brian Warner Owned by:
Priority: major Milestone: 0.1.7
Component: usability Version: 0.1.6
Keywords: Cc:

Description

The log message that says:

10:52:15 DEBUG 'twisted' [-] an inbound callRemote that we executed (on behalf of someone else) failed
10:52:15 DEBUG 'twisted' [-]  reqID=120, rref=<foolscap.broker.Broker object at 0xb3e752ec>, methname=getReferenceByName

should be enhanced to include the abbreviated !TubID of the broker that sent the message. This would be particularly helpful for getReferenceByName failures, since they indicate that some remote client has a stale FURL.

Change History (2)

comment:1 Changed 17 years ago by Brian Warner

Resolution: fixed
Status: newclosed

Closed, by [cc600fb8f9b525101bd82231f846d8dda7244739]. I added both local and remote TubIDs for both inbound and outbound messages. I also added the RemoteInterface? name to make the methname argument easier to figure out.

comment:2 Changed 17 years ago by Brian Warner

Milestone: undecided0.1.7
Note: See TracTickets for help on using tickets.