- 02 Mar, 2017 10 commits
-
-
Kostas Christidis authored
https://jira.hyperledger.org/browse/FAB-2603 1. Ledgers were maintained as directories inside a "blocks" directory. Semantically speaking, this doesn't quite make sense -- you'd expect to find blocks under a "blocks" directory. 2. The name of this directory should be an exported constant so that other packages can access it programmatically. The orderer package for instance, needs this info in order to construct the proper directories for its ledger. This changeset addresses both of these issues. Change-Id: I3bdf9763e227c29983003bab0769282136a42511 Signed-off-by:
Kostas Christidis <kostas@christidis.io>
-
Srinivasan Muralidharan authored
-
Yacov Manevich authored
-
Artem Barger authored
There is a package peer/util with file which no one uses in the current code base. Change-Id: Idbc6819e0e6ec428be4a94316357e0f63264a904 Signed-off-by:
Artem Barger <bartem@il.ibm.com>
-
Artem Barger authored
Peer cli command switched to use command line parameter to get the ordering service endpoint. This commit updates documentation files to reflect the change. Change-Id: Ib7d47d3bf6cb4cceb238a8514b0b1b960609448c Signed-off-by:
Artem Barger <bartem@il.ibm.com>
-
Gabor Hosszu authored
-
Angelo De Caro authored
This change-set does the following: 1. Refactors the mcs package to simplify mocking; 2. Implements the method VerifyBlock of the MessageCryptoService interface. 3. Tests This change-set should be merged together with https://gerrit.hyperledger.org/r/#/c/6321/ Change-Id: Ia4a1d92ee5ede55caaffe9a9b53afb2552308e2d Signed-off-by:
Angelo De Caro <adc@zurich.ibm.com>
-
Gennady Laventman authored
Single leader chosen, but not the peer is expected. Leader election mechanism works ok, need small test change. Disabling test until it fixed. Change-Id: I46d5816dba2de5a71e7c61d8f6575b648dd9b6e8 Signed-off-by:
Gennady Laventman <gennady@il.ibm.com>
-
Yacov Manevich authored
-
Luis Sanchez authored
https://jira.hyperledger.org/browse/FAB-2178 - orderer "file" ledger renamed to "json". - For now, "json" and "file" are synonymous values when specifiying LedgerType in orderer.yml. - The "json" ledger type re-uses the FileLedger configuration section in orderer.yml. Change-Id: I62798adec811fa887961089ce9eb85ddad80ce0c Signed-off-by:
Luis Sanchez <sanchezl@us.ibm.com>
-
- 01 Mar, 2017 21 commits
-
-
Artem Barger authored
Currently peer cli receives ordering service endpoint via environmental variable CORE_PEER_COMMITTER_LEDGER_ORDERER. Because ordering service endpoint will be provided with configuration transaction in the ledger block the env. variable will be depricate. This commit is 1 out of 3, takes care to switch peer cli to use new command line parameter, for example: peer channel create -o ordering_host:port .... Change-Id: I82fcb4f425d80489cb815b706b2d2d01b5e26827 Signed-off-by:
Artem Barger <bartem@il.ibm.com>
-
Christopher Ferris authored
-
Christopher Ferris authored
-
Gari Singh authored
https://jira.hyperledger.org/browse/FAB-2545 In order to get a test (or even real) system running, there is a lot of cryptographic material required: - root certificates for CAs (e.g. fabric-ca) - MSPs for organizations running peers - Local MSPs for peers - MSPs for ordererer organizations - Local MSPs for ordering nodes This CR adds a tool named "cryptogen" which will create these artifacts for you. It allows you to specify the number of peer organizations, the number of peers per organization and the number of ordering nodes (shims). It currently only creates a single orderer organization. To run, "./cryptogen" and it will display the command line options Change-Id: I15f135dc2893f7492566eb8ac5d02b2f4963ccd3 Signed-off-by:
Gari Singh <gari.r.singh@gmail.com>
-
Jim Zhang authored
-
denyeart authored
Invalid trans should not be written to history database. This will prevent writes from invalid trans from showing up in GetHistoryForKey() results. Change-Id: I8508094d697febf213098712185b3d6e9aaf9f29 Signed-off-by:
denyeart <enyeart@us.ibm.com>
-
Srinivasan Muralidharan authored
-
Yacov Manevich authored
-
Gari Singh authored
-
Gennady Laventman authored
Creation of leader election service during channel initialization in gossip and connecting between election callback to deliver service Change-Id: Ic2b8b1b5ebc770abcf4b935d39ce06087086b0c9 Signed-off-by:
Gennady Laventman <gennady@il.ibm.com>
-
Binh Nguyen authored
-
Chris Elder authored
Query is getting re-written in fabric with duplicate "data" wrappers. Query in chaincode: {"selector":{"docTypeId":3,"oriRe":"SMP","ctB":"CTB","valDt":"1990-12-24", "orB":"YYY","tD":"TD","cuVoB":52,"cuIoBu":"AA","cuSt":"NA"}} Result: 2017-03-01 06:48:14.782 UTC [statecouchdb] ApplyQueryWrapper -> DEBU 441 Rewritten query with data wrapper: {"selector":{"$and":[ {"chaincodeid":"marbles"}, {"data.cuIoBu":"AA","data.cuVoB":52,"data.data.ctB":"CTB","data.data.cuSt":"NA", "data.docTypeId":3,"data.orB":"YYY","data.oriRe":"SMP","data.tD":"TD" "data.valDt":"1990-12-24"}]}} Multiple fields have the "data" wrapper repeated. Change-Id: I50445f15222dbdf5bd61e475666c2c34fde6fda4 Signed-off-by:
Chris Elder <chris.elder@us.ibm.com>
-
Christopher Ferris authored
-
Christopher Ferris authored
-
Gennady Laventman authored
Leader election log output peer id (PKIid) as a string. In output it looks gibberish and grepping those logs not possible. This change print this PKIid as bytes array. Change-Id: Id02c1a8fe380db7d2300baf7afc6ff800c45108e Signed-off-by:
Gennady Laventman <gennady@il.ibm.com>
-
Gari Singh authored
-
Gari Singh authored
-
Yacov Manevich authored
-
Yacov Manevich authored
-
YACOVM authored
When the gossip comm layer is shutdown, the connection store is also shutdown as a result. While a connection is deleted/added, and the conn store is shutdown at the same time- a concurrent map read-write occures. Change-Id: I6ea84b3fb7e49a616a76d9cc0608a48dacb43bac Signed-off-by:
Yacov Manevich <yacovm@il.ibm.com>
-
Srinivasan Muralidharan authored
https://jira.hyperledger.org/browse/FAB-2557 Skipped some chaincode tests with rationale in comments. Will help reduce UT time. Change-Id: I74082c97fc9d474b35fe60edfe66fff4eca26f90 Signed-off-by:
Srinivasan Muralidharan <muralisr@us.ibm.com>
-
- 28 Feb, 2017 9 commits
-
-
Luis Sanchez authored
- included are small changes to the golang shim meant to help keep both shims similar. - added some behave tests Change-Id: Ib53fc58a97844648334c8319a4b806739cd363ae Signed-off-by:
Luis Sanchez <sanchezl@us.ibm.com>
-
Luis Sanchez authored
Matched the logic used to compute hash when installing a golang chaincode. Added some behave tests that can be run using: $ make behave-peer-chaincode or simply: $ cd peer/chaincode && behave Change-Id: If9747101c48754b26ce9c463f2adb7caef3220ad Signed-off-by:
Luis Sanchez <sanchezl@us.ibm.com>
-
Yacov Manevich authored
-
Tommy Back authored
https://jira.hyperledger.org/browse/FAB-2528 Change-Id: I118277195ba12e13b3a7a78a616d011e32e99574 Signed-off-by:
Tommy Back <tommy.back@iki.fi>
-
Yacov Manevich authored
-
Binh Nguyen authored
-
Gari Singh authored
-
Artem Barger authored
Peer cli chaincode command code has a few formatting and logging warning and inconsistences, this commit clean this issues. Change-Id: Iaf31daa3fcc63ca6b909ffbdf046e687fa7c16e4 Signed-off-by:
Artem Barger <bartem@il.ibm.com>
-
Ry Jones authored
This reverts commit 136e7035 . Change-Id: I912023654dc3ca57a6009ff584cc94c4d28b4aee Signed-off-by:
Ry Jones <rjones@linuxfoundation.org>
-