hyperledger
Here are 779 public repositories matching this topic...
-
Updated
Sep 28, 2021 - Go
-
Updated
Aug 4, 2021
-
Updated
Jul 15, 2021 - JavaScript
-
Updated
Mar 8, 2020 - JavaScript
-
Updated
Oct 4, 2021 - Python
-
Updated
Sep 14, 2021 - JavaScript
-
Updated
Sep 18, 2021 - Java
-
Updated
Apr 16, 2019 - C++
-
Updated
Oct 1, 2021 - JavaScript
-
Updated
Oct 14, 2021 - Go
-
Updated
Oct 15, 2021 - Python
The problem is that buffer array seems to have a different prototype than js definition and when convertBytetoString is called then:
for (const index in buffer_array) {
will start iterating over the prototype properties and result is incorrectly set to be a string of the function definitions instead of being empty string.
Could be fixed by adding a guard:
for (const index in buffer_array
-
Updated
Oct 23, 2019 - Makefile
-
Updated
Sep 26, 2020
-
Updated
Sep 27, 2021 - Go
-
Updated
Aug 21, 2021 - Python
When client sends request to endpoint /query, it expects as result VersionedQueryResult, but the peer returns QueryResult
-
Updated
Aug 30, 2021 - Go
-
Updated
May 12, 2021 - Python
-
Updated
Oct 16, 2021 - JavaScript
-
Updated
Aug 30, 2019 - JavaScript
-
Updated
Aug 25, 2018
-
Updated
Oct 13, 2021 - Shell
Please update the DID Resolver within ACA-Py for "did:sov" to follow the rules as recently updated in the DID Method spec. This means adjusting the returned DIDDoc to exactly what is documented in the DID Method spec for the cases of their being no endpoint ATTRIB, a "current convention" endpoint ATTRIB and support for the defined new convention endpoint ATTRIB.
The PR for the DID Method that hi
-
Updated
Jun 21, 2019
-
Updated
Sep 27, 2021 - JavaScript
-
Updated
Apr 21, 2021 - Shell
-
Updated
Oct 15, 2021 - Rust
Improve this page
Add a description, image, and links to the hyperledger topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the hyperledger topic, visit your repo's landing page and select "manage topics."
When installing a new chaincode on the peer you do get the package id of the chaincode which is good... this allows customers to use that data to go through the approve/commit steps.
However the issue is when they are reinstalling an existing chaincode there is nothing in the response to indicate the package id(hash). Install in that case returns a message that the chaincode already exists. We