1. 01 Jul, 2017 6 commits
  2. 30 Jun, 2017 3 commits
    • Christopher Ferris's avatar
      FAB-5139 fix branding issues · eaa7c2c3
      Christopher Ferris authored
      Change-Id: I60405320de34c35b21467802db4c4f0fa93d16da
      Signed-off-by: default avatarChristopher Ferris <chrisfer@us.ibm.com>
    • Christopher Ferris's avatar
    • yacovm's avatar
      [FAB-5052] [FAB-5051] Fine tune log messages · 2993534f
      yacovm authored
      In gossip when a peer obtains an AliveMessage from a peer it hasn't
      received its certificate yet - it complains in the log in WARNING that
      it has received a message from some peer it can't verify its identity.
      This is actually a common scenario where a peer is restarted and its
      in-meory certificate store is now empty, but the other peers contact
      the peer and send it alive messages which he can't verify until it syncs
      its certificates with them.
      This startles users and I think we should reduce the logging severity
      from WARN to DEBUG.
      When a peer is in a partition or is dead for a long enough time,
      gossip prints:
              Haven't heard from", <gibberish>, "for" <elapsed time>
      The problem is that the id is a string of a hash and its
      printed in gibberish.
      It's not something humans can read,
      and we need to cast the string back to []byte so it would be human readable.
      Change-Id: I94bcad11623e53b5275ef8cecbdd3f9563fa1e77
      Signed-off-by: default avataryacovm <yacovm@il.ibm.com>
  3. 29 Jun, 2017 6 commits
  4. 28 Jun, 2017 9 commits
  5. 27 Jun, 2017 13 commits
  6. 26 Jun, 2017 3 commits