1. 21 Feb, 2019 2 commits
  2. 20 Feb, 2019 1 commit
  3. 15 Feb, 2019 1 commit
  4. 14 Feb, 2019 1 commit
  5. 06 Feb, 2019 1 commit
  6. 05 Feb, 2019 1 commit
  7. 04 Feb, 2019 2 commits
    • Matthew Sykes's avatar
      [FAB-12942] use logfmt format for log fields · 2a8127f0
      Matthew Sykes authored
      Change-Id: Ibbbf4f55bd42a0914edc4b247c391e020b3a68a4
      Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
    • yacovm's avatar
      [FAB-13843] Fix cclifecycle test flake · 8a887975
      yacovm authored
      FAB-13471 Introduced a UT that does several (3) background listener updates.
      The test only waits for the listener updates to fire, but there is a log invocation
      that happens immediately afte the listener fires.
      The next test that runs, overwrites the logger's reference and thus a data race
      occurs (the previous test's spawned goroutine reads the logger's reference to write
      the log, while the next test replaces the logger reference.
      Fixed it by making the test wait until the log of the first test, logs
      the last message that is logged during the listener dispatch - 3 times.
      Ideally we'd have a logger instance for the production struct as a field,
      but this solution is far easier and has no production code change, so its
      surface area is smaller.
      Change-Id: Ia7ef144ae8574783b2b7a4925f47b51e966f8942
      Signed-off-by: default avataryacovm <yacovm@il.ibm.com>
  8. 28 Jan, 2019 1 commit
  9. 25 Jan, 2019 1 commit
  10. 24 Jan, 2019 1 commit
  11. 23 Jan, 2019 2 commits
  12. 21 Jan, 2019 1 commit
    • yacovm's avatar
      [FAB-13471] lifecycle to handle multiple updates · 908739e0
      yacovm authored
      The ledger calls several HandleChaincodeDeploy for each update
      but only a single ChaincodeDeployDone after all invocations
      to HandleChaincodeDeploy were made.
      The current implementation only supported a single update,
      and as a result - a second ChaincodeDeployDone will get stuck
      writing to a channel.
      This change set makes the Lifecycle in core/cclifecycle
      to be able to handle any number of updates in a single block.
      Change-Id: I1d85018af398bd5cb968e42031986a999f6be444
      Signed-off-by: default avataryacovm <yacovm@il.ibm.com>
  13. 18 Jan, 2019 1 commit
    • pama-ibm's avatar
      [FABCI-258] Fixed doc link · f118f2bc
      pama-ibm authored
      Fixed the docs badge
      link to point to the release branch
      of the doc. Also added a link to the
      Hyperledger Fabric rocket chat
      Change-Id: Icbe64888496ffda046d4e2668bd0caf100875454
      Signed-off-by: default avatarpama-ibm <pama@ibm.com>
  14. 17 Jan, 2019 1 commit
  15. 16 Jan, 2019 2 commits
  16. 15 Jan, 2019 2 commits
  17. 14 Jan, 2019 6 commits
  18. 13 Jan, 2019 1 commit
    • Matthias Neugschwandtner's avatar
      [FAB-13593] Ledger synchronization in SBE tests · d2fbc329
      Matthias Neugschwandtner authored
      The SBE integration tests include cases where the ledger is updated,
      waiting for the event on one peer and then checking the result on
      another peer. This patch adds synchronization that waits until both
      peers have the same ledger height, i.e. the transaction has been
      delivered to both peers.
      This is handled similarly in the private data integration tests.
      Change-Id: I6b68d3cf9cfeebf6cddd75003b3a946295fb4392
      Signed-off-by: default avatarMatthias Neugschwandtner <eug@zurich.ibm.com>
      (cherry picked from commit 0de5a321b98f60ab1060a2d1e1491880e22558f6)
  19. 12 Jan, 2019 4 commits
    • Artem Barger's avatar
      [FAB-13366] fix gossip state flake · 1b1118e5
      Artem Barger authored
      This commit removes time.Sleep() and instead waiting for peer to get
      connected with bootstrap peer to build membership before sending state
      Change-Id: If132432a710e3006fc9de0e9ea051709e6edbde6
      Signed-off-by: default avatarArtem Barger <bartem@il.ibm.com>
    • waels's avatar
      [FAB-11639]: Fix data races in gossip/discovery · 73cc36fe
      waels authored
      Change-Id: I6d5c6554ffe77079ee23c735f1ea89e3654f695f
      Signed-off-by: default avatarwaels <wael.shama@ibm.com>
      (cherry picked from commit e67eeb9bae8d25c7b072b7b2c6f6f0dcbc5becfe)
    • waels's avatar
      [FAB-11643]: Fix data races in gossip/state · c0644669
      waels authored
      Squashed with:
      [FAB-13377] revert stop discovery after chanState
      Change-Id: I17d89c3d0d84e634c5bdb477badcdfa2205d4ac7
      Signed-off-by: default avatarwaels <wael.shama@ibm.com>
      (cherry picked from commit 2fd63a497531f85937565e74e5a2c61a40fade1b)
    • muralisr's avatar
      add endorser metrics · 26aca2e3
      muralisr authored
      This CR adds endorser metrics
         - #proposals received
         - #successful proposals
         - #proposals that failed validation
         - #proposals that failed due to tx dup.
         - #proposals that failed due to endorsement
         - #proposals that failed chaincode instantiations
         - #duration of successful proposals
      Metrics from other parts in the stack such as chaincode are left
      to those components.
      FAB-13088 #done
      Change-Id: I16a472540b2cd6e31c93d89cce9b5e69940d2db4
      Signed-off-by: default avatarmuralisr <srinivasan.muralidharan99@gmail.com>
      Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      (cherry picked from commit 2d2cd3366bf7693e5e7545682fe1e55ed913512f)
  20. 11 Jan, 2019 5 commits
  21. 10 Jan, 2019 3 commits