1. 17 Jul, 2018 1 commit
  2. 11 Jul, 2018 3 commits
  3. 10 Jul, 2018 6 commits
    • Matthew Sykes's avatar
      [FAB-11053] extract config block helpers to nwo · 6e8d5564
      Matthew Sykes authored
      
      
      Change-Id: I4159e84a512a52bdba7917a03200c1614067ee7f
      Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      6e8d5564
    • Matthew Sykes's avatar
      [FAB-11052] begin adding nwo support for discovery · 5d808449
      Matthew Sykes authored
      
      
      Change-Id: Iac1be44a5a64d37467e83fac968c84796af7d38d
      Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      5d808449
    • Matthew Sykes's avatar
      [FAB-11051] refactor install/instantiate/upgrade · edec005f
      Matthew Sykes authored
      
      
      - remove InstallChaincode and InstantiateChaincode from network
      - create install, instantiate, and ensure instantiated helpers to
        deploy
      - create upgrade command and helpers
      
      Change-Id: I9b1395d41be25aba2e3f2067500b0ed265c1196a
      Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      edec005f
    • Jason Yellick's avatar
      Merge "[FAB-10967] SideDB video link" · 81fb533d
      Jason Yellick authored
      81fb533d
    • pama-ibm's avatar
      [FAB-10967] SideDB video link · 74161124
      pama-ibm authored
      
      
      Added a link to the private data video
      that D. Enyeart created to the private data
      tutorial (see additional resources
      in the tutorial TOC)
      
      Change-Id: Iac691b2882072324e9d0aa7eb9e02e4eccb544ce
      Signed-off-by: default avatarpama-ibm <pama@ibm.com>
      74161124
    • Matthew Sykes's avatar
      [FAB-10899] ignore context in VMController · 613e8450
      Matthew Sykes authored
      
      
      In go, a context is an object that carries cancellation signals across
      API boundaries. In fabric, contexts are associated with gRPC requests
      and get propagated through the system. When a request to invoke
      chaincode is received, the context is propagated to the controller
      responsible for managing container requests where it is misused.
      
      The controller spawns a go routine to handle the container request and
      signals completion via a channel. The Process function then waits for
      the request to complete or for the context to get canceled. When the
      context it canceled, the processor still waits for the request to
      complete before returning to the caller. This means the operation is
      never really canceled at this layer and, since it has to complete,
      it's likely that it has succeeded.
      
      Unfortunately, once the context is canceled, the controller returns the
      cancellation error from the context causing the callers to treat the
      operation as a failure.
      
      As the code downstream of the controller doesn't properly honor the
      context either and future releases remove it entirely, we'll simply
      ignore context cancellation signals in the controller.
      
      Change-Id: I51d8be9ef41e586c982abe268e6f9e0d61d4d7a7
      Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      613e8450
  4. 09 Jul, 2018 1 commit
    • pama-ibm's avatar
      [FAB-11102] Visual Vocab · 6d4bf4e7
      pama-ibm authored
      
      
      Added images from our visual vocabulary
      library to the Glossary & updated
      definition for Block. 
      
      Change-Id: I89f7694cd04c3828e3c48fdd2bb47b2178abcc85
      Signed-off-by: default avatarpama-ibm <pama@ibm.com>
      6d4bf4e7
  5. 08 Jul, 2018 4 commits
  6. 07 Jul, 2018 1 commit
    • Jason Yellick's avatar
      FAB-11094 Fix deadlock in block iterator · 375995ea
      Jason Yellick authored
      
      
      The deliver service used to not close ledger iterators until after a
      block had been committed.  With FAB-10799, the Deliver service more
      proactively cleans up ledger resources.  This leads to a more likely
      contention between the block iterator's Close() function and the Next()
      function.
      
      These two code paths acquire the same two mutexes, but in different
      orders.  The Next() path always acquires the itr.mgr.cpInfoCond.L first,
      then the itr.closeMarkerLock, while the Close() path inverts this order.
      If both Next() and Close() are invoked at the same time by goroutines,
      this can result in a deadlock where both mutexes lock and never unlock.
      
      This further prevents all blocks from committing and begins to leak
      memory resources.
      
      Change-Id: I99180fec2639a62cdf1cd9a6ce8b33f91ce498b9
      Signed-off-by: default avatarJason Yellick <jyellick@us.ibm.com>
      375995ea
  7. 06 Jul, 2018 3 commits
  8. 05 Jul, 2018 17 commits
  9. 04 Jul, 2018 2 commits
  10. 03 Jul, 2018 2 commits