V0.6 #3
Closed
V0.6 #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change-Id: I93ac3badea5ff6a3abf4c32af26468f6006f70cc Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>
This patch allows the sdk to handle multiple registrations on the same event criteria. It also enables registrations for all events for a particular chaincode. Change-Id: I2caa60e0080a8b41e9a8bf5d61ae671eaf09814a Signed-off-by: Patrick Mullaney <pm.mullaney@gmail.com>
This patch adds a series of chaincode event unit tests and addresses FAB-391 Change-Id: I7b77bbbfe8d4c12146cd4cc0e306eafe4491be58 Signed-off-by: Patrick Mullaney <pm.mullaney@gmail.com>
Modify build instruction for Java shim to
reflect publishing shim-client.jar to local Maven repo
FIX FAB-439
https://jira.hyperledger.org/browse/FAB-439
Change-Id: I2a2e87cad0fb7bc386f107e75389ffceafe3977c
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>
Fix FAB-578 incorrect chaincode signature in REST API fix rest_api.json Change-Id: If2258b09d89a79cdfa73e6897af737a5286ec436 Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>
This reverts commit 562a35f, reversing changes made to 4a78b41. This was done because we inadvertently merged a good chunk of master when patch a96b9ed was submitted to the v0.6 branch. We will cherry-pick a96b9ed in a later patch to restore the fix in the proper way. Change-Id: Ib16c0220e65697a68a5140960b82780c175d9fa2 Signed-off-by: Greg Haskins <gregory.haskins@gmail.com>
Fix FAB-578 incorrect chaincode signature in REST API fix rest_api.json NB: Cherry-picked from a96b9ed after reverting inadvertent merge of master - GMH Change-Id: I852de103d902d5630f27b43a8057e0ee82f1b020 Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com> Signed-off-by: Greg Haskins <gregory.haskins@gmail.com>
Change-Id: I5b1f0111984d5ba3304643bb30af2b9faa179467 Signed-off-by: Gregory Haskins <gregory.haskins@gmail.com>
added v1.0 preview added SDK to TOC added starter kit moved starter kit to top of TOC [ci skip] Change-Id: I20607bcd163289f0bfbdaa459952b3ae72112703 Signed-off-by: Nick Gaski <ngaski@us.ibm.com>
fix incorrect chaincode signatures in REST API and CLI [ci skip] Change-Id: I9ecbb3c4fe0b82ce1b22a6cf5cc34629e353da3e Signed-off-by: Nick Gaski <ngaski@us.ibm.com>
The update in npm 3 days ago in typedoc causes it to require typescript 2.0.3 which is not compatible with HFC 0.6. Resolved by locking down typedoc to 0.4.5. Change-Id: If1e47c7a372854d47ea89b2ab0c4be28f407b15a Signed-off-by: Jim Zhang <jzhang@us.ibm.com>
Target chaincode_example02 was updated by the hash was calculated wrong. Updating the target chaincode name hash to make the test pass. Change-Id: I7e6684b40fd4f369b34ad202ac7073e84628968a Signed-off-by: Jim Zhang <jzhang@us.ibm.com>
Strangely, when testing locally the target chaincode hash in the cc2cc unit test is calculated differently than when running on the build machine. Reverting the hash value back to what the test generates on the build machine. Change-Id: I0e192b6ca0c7385ec7f93746d0deb23b98dd4361 Signed-off-by: Jim Zhang <jzhang@us.ibm.com>
Fixes FAB-392 Supporting TLS between the ACA client the rest of the CA services. This feature requires changes to the configuration of the Membership Services (YAML file), adding the support for two newly added (YAML) configuration parameters under the security section of membersrvc.yaml. To enable this feature (TLS connectivity), one needs to specify that tls_enabled (=true) and a path to a PEM-encoded certificate file to use. There is also the option to use the serverhostname override, enforcing that the same TLS Server Certificate's Common Name to be used. Change-Id: I64444d0e21615a47662ba1388cd6901ff787b408 Signed-off-by: ASHUTOSH KUMAR <ashutosh_kumar@hotmail.com> Signed-off-by: JonathanLevi <jonathan@levi.name> Signed-off-by: Gari Singh <gari.r.singh@gmail.com>
changes required to test the fix for Fabric FAB-392 re-enable ACA+TLS unit test for node-sdk Updated getOptsFromOpts() in hfs.ts Updated eventHub setPeerAddr() in hfs.ts Added new tests: ../test/unit/member-api.js ../test/unit/getChain.js Change-Id: I3a1ad9a3f887720426ecd68de6bc4d1953f05eaf Signed-off-by: Allen Bailey <eabailey@us.ibm.com>
Change-Id: Ib00779035e9c05b7c077de492382dba3f8e73828 Signed-off-by: Gregory Haskins <gregory.haskins@gmail.com>
fixed nodesdk doc broken links and added permalinks and admonition in mkdocs.yml file. These changes improves user experience while using documentation through readthedocs. Change-Id: Ic24782898c70732c99565c72487973c8fbce8704 Signed-off-by: rameshthoomu <rameshbabu.thoomu@gmail.com>
Updating package.json to update the hfc version to 0.6.3 in order to publish the new package to NPM. Change-Id: I13a45ee0aabf9157a4c25a1f6e79b58ccf580213 Signed-off-by: Anna D Derbakova <adderbak@us.ibm.com>
|
Please submit your work to https://gerrit.hyperledger.org/ |
ghost
closed this
ghost
pushed a commit
that referenced
this pull request
Jan 21, 2018
This changes the main Vagrant mount point to hyperledger to provide access to all present hyperledger repositories, including fabric-samples. This will give access to new repos as they are added without requiring a modification of the Vagrantfile every time. Patch-set #1: adds fabric-samples to the list of mounted volumes if it exists Patch-set #2: fixes commit message Patch-set #3: changes strategy, mounting the parent directory to be future proof Patch-set #4: removed unrelated changes committed by error Change-Id: If126bd9d6d8806f149a0e6bacb1d8d34875f7ba4 Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
ghost
pushed a commit
that referenced
this pull request
Feb 18, 2019
This is the third of four (3/4) sub-tasks that focus on the "green" path of consensus-type migration from Kafka to Raft. By "green" we mean that there are no failures or aborts along the way. The 4 sub-tasks are staged in a way that minimizes dependencies between them. In this sub-task we introduce changes to the Kafka-base OSNs such that they implement the entire green path, until they commit migration and are ready to be restarted. This change concludes all the changes needed to implement the green path on the "Kafka" side. See respective JIRA item for further details. Note: some of the mocks had to be re-generated by couterfeiter to make the unit tests build. Change-Id: I2747f7d8017c344e9ff3bdd9dd98cbaa1480083f Signed-off-by: Yoav Tock <tock@il.ibm.com>
ghost
pushed a commit
that referenced
this pull request
Feb 18, 2019
ghost
pushed a commit
that referenced
this pull request
Mar 4, 2019
This is the third of four (3/4) sub-tasks that focus on the "green" path of consensus-type migration from Kafka to Raft. By "green" we mean that there are no failures or aborts along the way. The 4 sub-tasks are staged in a way that minimizes dependencies between them. In this sub-task we introduce changes to the Kafka-base OSNs such that they implement the entire green path, until they commit migration and are ready to be restarted. This change concludes all the changes needed to implement the green path on the "Kafka" side. See respective JIRA item for further details. Note: some of the mocks had to be re-generated by couterfeiter to make the unit tests build. Change-Id: I2747f7d8017c344e9ff3bdd9dd98cbaa1480083f Signed-off-by: Yoav Tock <tock@il.ibm.com> Signed-off-by: Artem Barger <bartem@il.ibm.com>
ghost
pushed a commit
that referenced
this pull request
Jun 7, 2019
ZhAnGeek
pushed a commit
to ZhAnGeek/fabric
that referenced
this pull request
Oct 16, 2021
TonyWu3027
added a commit
to alfredomusumeci/fabric
that referenced
this pull request
Aug 14, 2023
Blocc protocol
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Motivation and Context
Fixes #
How Has This Been Tested?
Checklist:
Signed-off-by: