* changes:
  FAB-10830 GetDeploymentPackage to take string
  FAB-10829 Remove unused java hash file/function
  FAB-10828 ValidateDepSpec to ValidateCodePackage
  FAB-10827 Remove meaningless file write from test
  FAB-10826 Change ValidateSpec to ValidatePath

.. in ExtractStatedbArtifactsForChaincode

Change-Id: I9387cb2162537a5007403541093e547f24953b17
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Icc8d1ee55b4d0a00a6084a081faf59a8fa7e52a2
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Ie87069983c185dca5756be5a681c5634de89258f
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: I4159e84a512a52bdba7917a03200c1614067ee7f
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Iac1be44a5a64d37467e83fac968c84796af7d38d
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

- 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: Matthew Sykes <sykesmat@us.ibm.com>

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: pama-ibm <pama@ibm.com>

This is part of the hygiene work to stop using external messaging protos
to pass state internally.

Change-Id: I13a03631de57292f7e7b52294c126635749402f6
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Make the parameters to the platforms functions explicit rather than
using the chaincode spec structures.

Change-Id: I3139c843750d54b6085633d863566b145d4499c5
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

This CR completes the work of removing the chaincode spec and chaincode
deployment spec from the platforms.Platform interface.  There is some
outstanding work remaining to remove it entirely from the package which
will follow this CR.

Change-Id: Ib7d56d88267b72eb5de95ad382c8d59c581d2d55
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

The ccmetadata is imported by utils and by other platforms, but is also
part of the platforms interface definitions itself.  This CR moves the
interface definition into the platforms package where it belongs, and
also updates the implementation to accept an interface instead of
requiring the chaincode deployment spec.  It is part of a series to
remove the deployment spec from the platforms package.

Change-Id: I7ab07c98a88fdf67129c29320ac1433e8b466695
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Continuing a series of removing the chaincode spec dependencies from the
platforms package.

Change-Id: I23f108d895078db80d9b6ff1f733d27a71d5f548
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

The CDS is never actually used in any capacity for GenerateDockerfile
so, this CR removes it from the interface definition.

Change-Id: I95f595d9877d2e76229ce1b13be197e288e57af1
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Part of the ongoing series to remove the chaincode protos from the
platforms package, this CR passes in "path" explicitly as a string to
GetDeploymentPackage, as it was the only piece fo the chaincode spec
beign used.

Change-Id: Ifaa8a16bdbeae84c479a8e33a9abc47ef175c551
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

The java platform comment claims that the call to the hash computation
function affects the tar writer, but it does not in fact, and the hash
is discarded, so, this is all useless code. Removing.

Change-Id: Iad9c9bbbd4bdb7805f4d234db4091a1fad3448b2
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Part of an ongoing series to remove all references to the chaincode
protos from the platforms package so that they can eventually be
replaced.  ValidateDeploymentSpec was only ever inspecting the code
package bytes and nothing else about the spec, so changing this method
to take the bytes directly.

Change-Id: I897028f3bf4ea9818f685d01fba09ede5783637d
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

The node platform test currently creates a dummy file, then stats it and
reads it in, then creates a tar header from the stat result, then
modifies the tar header.  All of this is unnecessary code when the test
can simply create the tar custom tar header directly.  This CR does just
that.

Change-Id: I9ea0ada2df5441b102faf7ead3ecc9457c7b3d93
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

This is part of a CR series to remove the explicit dependency of the
chaincode spec and deployment spec from the platforms package.
Ultimately, these messages were designed for fabric v0.5/v0.6 and would
not have been recycled given more time.  This is a step in allowing us
to use a different, more fabric v1.0 natural format for describing
chaincodes.

Change-Id: Ibbd20f3ce85f226e4c2cc03b3e2fd70081815ba6
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

The linter checking ignores the new added `cmd` pkg.
This patchset will let linter check the `cmd` pkg, too.

Change-Id: If51d66a918eae5f7422e47bbef58c0b1452baf2a
Signed-off-by: Baohua Yang <yangbaohua@gmail.com>

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: Matthew Sykes <sykesmat@us.ibm.com>

Added images from our visual vocabulary
library to the Glossary & updated
definition for Block. 

Change-Id: I89f7694cd04c3828e3c48fdd2bb47b2178abcc85
Signed-off-by: pama-ibm <pama@ibm.com>

Change-Id: Iade2372bc4708277adb3979e50393331bf8cc378
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

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: Jason Yellick <jyellick@us.ibm.com>

PvtDataDigest is a protobuf message that is used in the gossip private data
implementation.

The latest version of protobuf generates functions to protobuf structs,
which prevents using protobuf messages as map keys.

This change set moves the code to use an equivalent struct
that has the same fields but without functions.

Change-Id: Icdfdffb98625cb7ace37d6c0227906971e05fcc7
Signed-off-by: yacovm <yacovm@il.ibm.com>

FAB-11060

Update the CHANGELOG on master since
that's what we point to.

Also added the v1.1.0 changelog (as it was
missing) and renamed v1.2.0-rc1 to v1.2.0

Change-Id: I275baa0242748a721e041d5408ded397c634d088
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>