1. 14 Mar, 2019 1 commit
  2. 18 Jan, 2019 1 commit
    • pama-ibm's avatar
      [FABCI-258] fixed doc link · 8ed385b6
      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: I60f4c637bde7cd28dd7a89ec486d60236a07eda5
      Signed-off-by: default avatarpama-ibm <pama@ibm.com>
      8ed385b6
  3. 20 Dec, 2018 1 commit
  4. 06 Nov, 2018 1 commit
  5. 17 Oct, 2018 1 commit
  6. 16 Oct, 2018 1 commit
  7. 27 Sep, 2018 1 commit
  8. 19 Sep, 2018 1 commit
  9. 26 Jul, 2018 1 commit
  10. 14 Jul, 2018 1 commit
  11. 15 Jun, 2018 1 commit
  12. 29 Apr, 2018 1 commit
  13. 17 Apr, 2018 1 commit
  14. 06 Apr, 2018 1 commit
  15. 13 Mar, 2018 1 commit
  16. 09 Mar, 2018 1 commit
    • yacovm's avatar
      [FAB-8575] Missing nil check in VSCCValidateTx · 84a7e5ce
      yacovm authored
      
      
      There is a missing nil check in the function VSCCValidateTx in case
      the header extension's ChaincodeId is nil.
      
      I added a nil check for that, and for the ChaincodeAction too
      
      Change-Id: I00e183cccf14ba8d6078b40db095f5225234a11d
      Signed-off-by: default avataryacovm <yacovm@il.ibm.com>
      (cherry picked from commit f055bdacebdff6b02171e09e97d0a15f541b0c4b)
      84a7e5ce
  17. 08 Mar, 2018 1 commit
  18. 07 Mar, 2018 1 commit
    • yacovm's avatar
      [FAB-8688] Gossip onConnect() references wrong field · db261050
      yacovm authored
      
      
      In gossip, when a peer p contacts peer q and tries to connect
      to it, while it's already connected to it - q closes the current
      connection with p and replaces it with q.
      
      However, the code referenced the identity field instead of the
      pki-id field and thus it always replaced the connection,
      without closing the previous connection.
      
      Change-Id: I021ce246ce3735aa9e3451f20590fd119737a310
      Signed-off-by: default avataryacovm <yacovm@il.ibm.com>
      db261050
  19. 18 Feb, 2018 2 commits
  20. 07 Feb, 2018 2 commits
  21. 06 Feb, 2018 1 commit
    • yacovm's avatar
      [FAB-8075] Peer Deliver client doesn't failover to OSN · 0d922fb5
      yacovm authored
      
      
      If the peer is connected to a specific ordering node, and no
      blocks are received within a timely manner, when that ordering
      node loses connection - the peer gives up connecting to a different
      ordering node.
      
      This is because the total elapsed time includes the time waiting
      on the Recv() and it instead should only include the time
      that is spent while sleeping because of the exponential backoff.
      
      Change-Id: I4a75dad1f1fa2facf70498a3d9692598b89e8a44
      Signed-off-by: default avataryacovm <yacovm@il.ibm.com>
      0d922fb5
  22. 01 Feb, 2018 1 commit
  23. 30 Jan, 2018 1 commit
  24. 25 Jan, 2018 2 commits
  25. 12 Dec, 2017 1 commit
    • Gari Singh's avatar
      [FAB-7434] Normalize UID/GID in cc packages · 78e18d17
      Gari Singh authored
      
      
      When creating a chaincode package, if
      one uses the same code but it happens
      to be owned by a different user/group,
      a different package is produced and this
      can result in a fingerprint mismatch
      at instantiate time.
      
      While people should actually install the
      same package and not individually create
      their own packages, creating packages
      given identical inputs/code should be
      repeatable on different machines so
      this CR simply normalizes the UID/GID
      when adding files to the archive.
      
      Change-Id: I04b6ddde00bc80d98cf55de66ae9ff005f6b2aa7
      Signed-off-by: default avatarGari Singh <gari.r.singh@gmail.com>
      78e18d17
  26. 08 Dec, 2017 1 commit
    • manish's avatar
      [FAB-7156] Fix for an error ignored in commit path · a8728bc0
      manish authored
      
      
      A specific error (when during validation trying to get the
      current version of an item from the db) is ignored. This
      results in a non-deterministinc behavior because the error
      could happen only on a few peers (e.g., couchdb is inaccessible from the peer).
      
      This CR propagates the error up which would result in returing the block commit
      operation with an error instead of marking the transaction as invalid on the
      peer facing intermittent issue with db.
      
      Change-Id: I4022196cd8c8200891f52f6b7a69c8a062c793cd
      Signed-off-by: default avatarmanish <manish.sethi@gmail.com>
      a8728bc0
  27. 07 Dec, 2017 1 commit
  28. 06 Dec, 2017 1 commit
  29. 05 Dec, 2017 2 commits
  30. 04 Dec, 2017 3 commits
  31. 29 Nov, 2017 1 commit
  32. 27 Nov, 2017 2 commits
  33. 26 Nov, 2017 1 commit
    • Gari Singh's avatar
      [FAB-6987]Fix single_tx_client panic error · dc8d3234
      Gari Singh authored
      
      
      Likley due to the fact that it has not
      really been maintained, the
      single_tx_client panicked because
      the proper message structures were
      not being send to the orderer.
      
      Once this was fixed, it led to
      a type mismatch error due to the
      way the deliver channel is set up.
      
      Rather than muck around with this, I
      simply got the client working such that
      it gets the latest block from the orderer
      and then also gets the block for the tx it
      submits as well.
      
      Change-Id: Ie05ac79a2d940e2b30b1d8935bb2feeea527518b
      Signed-off-by: default avatarGari Singh <gari.r.singh@gmail.com>
      dc8d3234