ExecuteQuery() is not supported on leveldb state
database.  Currently if called it will panic the peer.
This changeset changes it to a normal error
so that it does not kill the peer process.

Change-Id: Ib9f525524c99b107b4fc3935f2d38a5657bace73
Signed-off-by: denyeart <enyeart@us.ibm.com>

JSON produced by GetQueryResult() is not valid if there
are multiple records returned.  Need to add a comma
before each JSON member (except for the first).

Change-Id: I1d7586f888674a2251fa5578b1bc00faa3a73dbc
Signed-off-by: denyeart <enyeart@us.ibm.com>

This changeset introduces a new chaincode example marbles02.

marbles02 is a stripped down version of marbles providing
examples of various ledger interaction patterns:
-PutState()
-GetState()
-DelState()
-PartialCompositeKeyQuery() range query
-Creation of key/value 'indexes' for efficient range queries.
-Parameterized rich query (requires CouchDB to execute)
-Ad hoc rich query (requires CouchDB to execute)
-History of key values (coming soon)

Similar to example02, marbles02 is a simple chaincode
that can be use by anybody that wants to try out the fabric.
Unlike example02, marbles02 chaincode data is based on JSON,
enabling chaincode query.

Change-Id: I37b7074f6364ab726ba3ec760fffd2b07a9eb543
Signed-off-by: denyeart <enyeart@us.ibm.com>

Peer leadership status change callback signature
This callback invoked once peer become leader or give up on leadership
And it passed as argument to NewLeaderElectionService, can be nil

Change-Id: Ib0ef831f84428e3505cd4a69feb6135b57660e1d
Signed-off-by: Gennady Laventman <gennady@il.ibm.com>

Address review comments from:
https://gerrit.hyperledger.org/r/#/c/4767/



Updates to logging and comments per Murali's feedback.

Rename ExecuteQuery() to GetQueryResult() per Binh's feedback.
The rename is only made at the top level chaincode function
The name change will be propagated to all the underlying
helper functions and messages as part of a larger refactor that
Murali has planned for post-alpha.

Fix handler.go result type (KV should be QueryRecord).

Tested that chaincode calls to GetQueryResult() work end-to-end.

Change-Id: I9cda95bab237e03880243be0b15110d119f033e8
Signed-off-by: denyeart <enyeart@us.ibm.com>

This change-set implements the gossip MessageCryptoService and
SecurityAdvisor. This implementation will be used by
a peer to initialiaze the gossip layer.

What remains to do is to integrate the channel read
policies once they are in place.

This change-set comes in the context of JIRA item:
https://jira.hyperledger.org/browse/FAB-1394


Notice that before starting using the implementation
provided by this change-set, the implementation of
identity.GetOrganizationUnits() and the enforcement
that DeserializeIdentity fails when the mspIDs do not match
must be in place.

Change-Id: I8b9cbe90044de14a68ba78ce5f7391f9e5da2cd0
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

https://jira.hyperledger.org/browse/FAB-1884


This adds fabric-ca documentation to readthedocs

Change-Id: I8f1e7249d0d45c457e07782c59e3ecaa32864fc6
Signed-off-by: Keith Smith <bksmith@us.ibm.com>

relative links might
be the issue - removed
for now.

Fixed relative links
Tweaked some words
WIP
[ci skip]

Change-Id: Id92c814832b0a765122e5c0e2487430486369d5f
Signed-off-by: Joshua Horton <joshh@us.ibm.com>

This code captures all output from stdout/stderr originating from
our peer-launched docker containers and stuffs it into a custom
logger on a per-chaincode basis.  It is enabled by the configuration
knob "CORE_VM_DOCKER_ATTACHSTDOUT=true" and defaults to disabled.
This should allow an admin or developer to enable this log at their
discretion to assist with debugging container problems, while
minimizing risk for malicious/faulty chaincodes to threaten the
peer with unmitigated logging.

Change-Id: I3f36958c41f14981e2e0f412b7e46589e6fa7110
Signed-off-by: Greg Haskins <gregory.haskins@gmail.com>

This is the content
placeholder for why
fabric
WIP

[ci skip}

Change-Id: I4a42cf9247e9965c2072debbfcbf7666281cee9d
Signed-off-by: Joshua Horton <joshh@us.ibm.com>

When the peer joins a channel it gets a list of anchor peers.
We need the gossip layer to reach out to these anchor peers
and connect to them.

- Added 2 tests (one in the discovery module and one in the gossip module)

I tested this using the following setup:
used docs/docker-compose-channel.yml
And added another peer, and didn't give that peer a bootstrap peer,
so both peers don't know of each other at startup.
Then I created an anchorPeer file with the ip address (172.21.0.4)
and port of one of the peers.
After that, I created a channel with that anchor peer file,
and made the other peer to join the channel.
The peer tried contacting the anchor peer (looked at the gossip communication logs)
and tried authentication with it:
Sending tag:EMPTY signature:"[xxx]" conn:<pkiID:"172.21.0.4:7051" cert:"[yyyyy]" >  to 172.21.0.4:53637
WARN 213 Remote endpoint claims to be a different peer, expected [PEM FILE]
but got [fake PKI-ID I use until MSP is integrated with gossip]

This proves that when joinChannel is called upon a peer with
suitable anchor peer configuration, the peers try to connect
to one another.

Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>
Change-Id: Ia033f81eeaf38cb53cb65dc06a01dca07342386b

Change-Id: I6d8199bb2350faea728921fe6e058ebb180197d2
Signed-off-by: Luis Sanchez <sanchezl@us.ibm.com>

Oracle JVM option -Xloggc does not work on IBM JVM.

Change-Id: Ib0fdc2aab0f7bc6fbe4c5de783affc403b8b48e8
Signed-off-by: Luis Sanchez <sanchezl@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1873



Set the ENV in images/peer/Dockerfile.in as well

Change-Id: I6a8d57748eb9c59db81599894aa608d8ebd25d8d
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

Getting a panic error when committer receives a config block
and attempts to write the tran to history db.
Fixed by only writing to history db for endorsement transactions.

Change-Id: I32d5e414199d85355eeae84f3e1ae680fe0811f0
Signed-off-by: denyeart <enyeart@us.ibm.com>

This changeset trims the MSP plaintext message in the log statement
to the beginning and end of the byte array if its length is greater
than 32. Logging the entire plaintext for very long messages can
lead to the process hanging when deploying chaincode.

https://jira.hyperledger.org/browse/FAB-1870



Change-Id: I0d169df859c0be97090c86ff73f014d813ea7cdd
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>

Motivation for this change:
Maintain the version inline with the document, without changing the
structure/value of the stored document.  This will prevent unexpected
data values being returned and will prevent possible name collisions
with document values.

- Create a data wrapper for ledger JSON data stored in CouchDB.

- Return the version based on block number and transaction id

The wrapper will be implemented as a new key named "data" which will
contain the JSON data for the state database.

Prior to change example:

"doc": {
 "_id": "2",
 "_rev": "2-8ee0c31b21ad650e5b872c0b98e59ab5",
 "version":"1:2"
 "asset_name": "marble2",
 "color": "red",
 "owner": "tom",
 "size": "25"
}

 Following change:

 "doc": {
  "_id": "2",
  "_rev": "2-8ee0c31b21ad650e5b872c0b98e59ab5",
  "version":"1:2"
  "data": {
   "asset_name": "marble2",
   "color": "red",
   "owner": "tom",
   "size": "25"
  }
 }

Change-Id: I59391ea926531c46c346fc8448e3d041ca5f3fdf
Signed-off-by: Chris Elder <chris.elder@us.ibm.com>