forks/go-ethereum
1
0
Fork 1
mirror of https://github.com/ethereum/go-ethereum.git synced 2026-07-23 05:06:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

improve request log messages

Browse source
This commit is contained in:
zelig 2015-05-14 13:38:09 +02:00
parent c14c85f03b
commit 7c5d2b8755
1 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
bzz/protocol.go
View file

@ -95,6 +95,10 @@ type statusMsgData struct {
// Strategy uint64
}
func (self *statusMsgData) String() string {
return fmt.Sptintf("Status: Version: %v, ID: %v, NodeID: %v, Addr: %v, NetworkId: %v, Caps: %v", self.Version, self.ID, self.NodeID, self.Addr, self.NetworkId, self.Caps)
}
/*
Given the chunker I see absolutely no reason why not allow storage and delivery of larger data . See my discussion on flexible chunking.
store requests are forwarded to the peers in their cademlia proximity bin if they are distant
@ -251,7 +255,7 @@ func (self *bzzProtocol) handle() error {
switch msg.Code {
case statusMsg:
dpaLogger.Debugf("Status message: %#v", msg)
dpaLogger.Debugf("Status message: %v", msg)
return self.protoError(ErrExtraStatusMsg, "")
case storeRequestMsg:
@ -267,7 +271,7 @@ func (self *bzzProtocol) handle() error {
if err := msg.Decode(&req); err != nil {
return self.protoError(ErrDecode, "->msg %v: %v", msg, err)
}
dpaLogger.Debugf("Request message: %#v", req)
dpaLogger.Debugf("Request message: %v", req)
if req.Key == nil {
return self.protoError(ErrDecode, "protocol handler: req.Key == nil || req.Timeout == nil")
}
@ -375,7 +379,7 @@ func (self *bzzProtocol) peerAddr() *peerAddr {
// outgoing messages
func (self *bzzProtocol) retrieve(req *retrieveRequestMsgData) {
dpaLogger.Debugf("Request message: %#v", req)
dpaLogger.Debugf("Request message: %v", req)
err := p2p.Send(self.rw, retrieveRequestMsg, req)
if err != nil {
dpaLogger.Errorf("EncodeMsg error: %v", err)