akovalenko/lnd.xprv
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

funding: properly display our 1-byte error code messages

Browse Source
This commit is contained in:
Olaoluwa Osuntokun 2017-12-06 18:43:51 -08:00
parent cc3b32c0d4
commit 4444ec39ea
No known key found for this signature in database
GPG Key ID: 964EA263DD637C21
2 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
fundingmanager.go
View File

@ -2220,7 +2220,7 @@ func (f *fundingManager) handleErrorMsg(fmsg *fundingErrorMsg) {
// If this isn't a simple error code, then we'll display the entire // If this isn't a simple error code, then we'll display the entire
// thing. // thing.
if len(protocolErr.Data) > 0 { if len(protocolErr.Data) > 1 {
resCtx.err <- grpc.Errorf( resCtx.err <- grpc.Errorf(
lnErr.ToGrpcCode(), string(protocolErr.Data), lnErr.ToGrpcCode(), string(protocolErr.Data),
) )

2
peer.go
View File

@ -596,8 +596,6 @@ func newChanMsgStream(p *peer, cid lnwire.ChannelID) *msgStream {
// to the other side, they immediately send a // to the other side, they immediately send a
// channel update message, but we haven't yet // channel update message, but we haven't yet
// sent the channel to the channelManager. // sent the channel to the channelManager.
peerLog.Infof("waiting on chan open to deliver: %v",
spew.Sdump(msg))
p.server.fundingMgr.waitUntilChannelOpen(cid) p.server.fundingMgr.waitUntilChannelOpen(cid)
} }