Change-Id: I93ac3badea5ff6a3abf4c32af26468f6006f70cc
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

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

This patch fixes two problems in commit e5a81bb6

.

1) There was a problem where the #comment after the IS_RELEASE
variable was casuing the conditional logic to assume this was
a -snapshot release.

2) We collectively agreed that -developer-preview is a bit
of a mouthful for the release taxonomy and this should be
shortened to -preview

This has been confirmed to now drive the proper conditional
generation of a release tag and use the desired "-preview".

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

A tag should be created against this commit

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

     Changes:
        modified:   docs/Setup/NodeSDK-setup.md
        modified:   docs/index.md
        new file:   docs/nodeSDK/app-developer-env-setup.md
        new file:   docs/nodeSDK/app-overview.md
        new file:   docs/nodeSDK/node-sdk-guide.md
        new file:   docs/nodeSDK/node-sdk-indepth.md
        new file:   docs/nodeSDK/node-sdk-self-contained.md
        new file:   docs/nodeSDK/sample-standalone-app.md
        new file:   docs/nodeSDK/sample-web-app.md
        new sample file:   examples/sdk/node/standalone-app.js
        new sample file:   examples/sdk/node/web-app.js

Change-Id: I65f0f470806bc66a28d151780e1f36cf05b509df
Signed-off-by: Bret Harrison <beharrison@nc.rr.com>

This patch changes the peer snapshot retrieval
logic from a non-blocking channel write to a
blocking channel write with a timeout.  This allows
gRPC's own buffering mechanisms to apply back pressure
when sending large state snapshots.

Additionally, this change will suppress some of the
spammy log messages which can flood logs when the
correlation id gets out of sync.

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



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

Merging in TLS related changes from previous work which
were mistakenly left out of this branch. These changes
were originally made and tested on the Fabric05 branch.

Fixes FAB-374

Change-Id: If5b482d00297d840924dab78f35824a4245e1f02
Signed-off-by: Anna D Derbakova <adderbak@us.ibm.com>
Signed-off-by: Allen Bailey <eabailey@us.ibm.com>

This changeset validates state at startup, switching the
assumption from state being valid to state being invalid.

Further, once state transfer completes, the replica will
now broadcast a checkpoint for the state it transferred to.

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



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

This patch adds support for fabric events to the SDK. It defaults to
the same timer based mechanism for transactional events if the app
doesn't connect to a peer event source(eventHubConnect).

Change-Id: Ib9f9f79f11438eb67d5ada7666ce1d117af511a5
Signed-off-by: Patrick Mullaney <pm.mullaney@gmail.com>

FIX FAB-158

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



Change-Id: I79aae2b4e537a20a72b2fcc1bf83a40087cfeed6
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

Currently, the Node.js SDK unit tests are cloning the
master branch from Gerrit in order to include it as a
dependency inside pre-built chaincode packages. That
causes the unit tests to fail on all other branches
except the master branch. Until the fabric dependency
is entirely removed from the SDK unit tests, the test
script will instead use the local copy of the fabric
project to avoid cloning the dependency directly from
master. This avoids unit test failures due to
incompatible versions.

Change-Id: I995d16b98f1e8d337a8cd44c87133c92542437d0
Signed-off-by: Anna D Derbakova <adderbak@us.ibm.com>

Modify the transaction id for a deployment transaction
to the chaincode hash. The Txid was being incorrectly
set to a generated UUID.

Fixes FAB-288

Change-Id: I69736e05e2240b79ae3bb5bf378abf519ebbf993
Signed-off-by: Anna D Derbakova <adderbak@us.ibm.com>

Remove remaining references to "account" parameter,
which was previous removed from the ECert and the
registration request.

Change-Id: Ia4233af3f711175910911a3469b29789c5238e44
Signed-off-by: Anna D Derbakova <adderbak@us.ibm.com>

Change 'Given I start peers' to 'Given I start peers, waiting up to
"<time>" seconds for them to be ready', reusing the functions created
for intelligently starting used in 'Given we compose <compose-file>'.

Modify the issue_1874b test to wait for the transaction invoked
during vp0's down time to be committed instead of implicitly
accomplishing this during the wait for 15 seconds statement.

Change-Id: Ib4b00a6d4eb1dfb50f065cba7ac1d4804f447798
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

Change 899 introduced a new unit test for the node sdk
which causes the node sdk unit tests to fail.  The fix was to
change the chaincodeID from mycc3 to mycc4 for the new test.
This amends FAB-285

Fixes FAB-285

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

Currently only local deployment of Java chaincode is supported.

Change-Id: Id7651f6eeae232260f76f2280b935f7c9a15d169
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

There have been a number of instances of BDD tests which were
starting correctly but due to high load on the Jenkins host were
unable to complete prior to the timeout expiry.

This can been seen in action during
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-behave-x86_64/19/


in the chaincode authorizable counter test. Looking at the peer logs
it can be seen that peers vp1, vp2, and vp3 started up in 9, 1 and 5
seconds respectively. vp0 however timed out and didn't start.

Increasing the timeout from 10 to 20 seconds for peers to connect to
membersrvc and from 15 to 30 seconds overall to combat this.

Change-Id: I5c45697a63b95dd31371f423d274de69f0dc5cd3
Signed-off-by: Julian Carrivck <cjulian@au1.ibm.com>

The log prefix should be "stop" in DockerVM.Stop.

Change-Id: I551b37f62238791ce9506aad2c558c7bca73c81f
Signed-off-by: jiangyaoguo <jiangyaoguo@gmail.com>

Move the BDD Docker compose files into a new sub folder so they are all
in one place and do not clog up the root of the bddtests/ folder.
While altering logic to determine the container names I also refactored
the Docker-Compose parsing code to make it more clear as to what it was
doing (parseComposeOutput in bdd_compose_util.py).

I needed to add a dummy compose-defaults.yml file so that CI would
successfully pass. When this change makes it into all branches then it
can be removed and the CI scripts updated.

I also changed the permissions on a couple of the bdd files from 755 to
644.

Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>
Change-Id: Iefd1007e79ee3827d39ed9b0bdec327f30e0c39f

when receive a rejection event with no "-listen-to-rejections",
adapter of block-listener push a nil to notfy channel. This will
cause nil pointer panic. Fix the handle logic.

Change-Id: I8391af03acf32c6d99d613db6e2e7dc13d2424cc
Signed-off-by: jiangyaoguo <jiangyaoguo@gmail.com>