Branch: refs/heads/master
Home: https://github.com/btcsuite/btcd
Commit: 214d975adfafbd9b4eca85363a0124a8e88cff58
https://github.com/btcsuite/btcd/commit/214d975adfafbd9b4eca85363a0124a8e88cff58
Author: Dave Collins <da...@conformal.com>
Date: 2016-10-28 (Fri, 28 Oct 2016)
Changed paths:
M server.go
Log Message:
-----------
server: Notify connmgr if server peer assoc fails.
This corrects a few issues introduced with the connection manager where
the server was not notifying the connection manager when a connection
request is available again.
The cases resolved are:
- Unable to initialize a server peer instance in response to the connection
- Failure to associate the connection with the server peer instance
- Disconnection of a non-persistent outbound peer
It also changes the log message to a debug in the former case because
it's not something that should be shown to the user as an error given
it's not due to anything the user has misconfigured nor is it even
unexpected if an invalid address is provided.
Commit: 05126f6034918027faf4256b51f67f92875c150a
https://github.com/btcsuite/btcd/commit/05126f6034918027faf4256b51f67f92875c150a
Author: Dave Collins <da...@conformal.com>
Date: 2016-10-28 (Fri, 28 Oct 2016)
Changed paths:
M peer/peer.go
Log Message:
-----------
peer: Use debug log for inability to start peer.
The inability for a peer to negotiate is not something that should be a
warning which implies something is wrong. On the contrary, it is quite
expected that various peers will connect (or be connected to) that are
unable to properly negotiate for a variety of reasons. One example would
be a peer that is too old.
Also, while here take care of a few style nits.
Compare: https://github.com/btcsuite/btcd/compare/a1f014c9e180...05126f603491
