|
Re: Issues w/ tutorial: Build Your First Network
Why don't you use "byfn.sh" script to run the whole things, or you want to run it step by step.
Why don't you use "byfn.sh" script to run the whole things, or you want to run it step by step.
|
By
Kimheng SOK
·
#7652
·
|
|
Re: Issues w/ tutorial: Build Your First Network
Salmon,
You can give this a try. It is a lot easier. litong01/minifabric
litong01/minifabric
Stand up fabric network on a single machine. Contribute to litong01/minifabric development by creating
Salmon,
You can give this a try. It is a lot easier. litong01/minifabric
litong01/minifabric
Stand up fabric network on a single machine. Contribute to litong01/minifabric development by creating
|
By
email4tong@gmail.com
·
#7651
·
|
|
Re: Peer communication during chaincode execution
See https://jira.hyperledger.org/browse/FAB-11980
May I ask why do you need it? what'syour use case?
From: "Kimheng SOK"<sok.kimheng@...>
To: hyperledger-fabric@...
Date: 01/29/2020
See https://jira.hyperledger.org/browse/FAB-11980
May I ask why do you need it? what'syour use case?
From: "Kimheng SOK"<sok.kimheng@...>
To: hyperledger-fabric@...
Date: 01/29/2020
|
By
Yacov
·
#7650
·
|
|
Issues w/ tutorial: Build Your First Network
Hi,
I’m having issues in this tutorial and I’m not sure why or how to resolve it. I follow every step exactly but when in bash I enter the command:
#peer channel create -o
Hi,
I’m having issues in this tutorial and I’m not sure why or how to resolve it. I follow every step exactly but when in bash I enter the command:
#peer channel create -o
|
By
esalmon@...
·
#7649
·
|
|
Re: Chaincode gets instantiated but not able to invoke or list it
#fabric
#fabric-chaincode
Hey mrudav,
Did you make any progress on this? I am trying the same and it also fails at initializing the chaincode. On the worker node I can see that the chaincode container is started with a log
Hey mrudav,
Did you make any progress on this? I am trying the same and it also fails at initializing the chaincode. On the worker node I can see that the chaincode container is started with a log
|
By
stefan.riembauer@...
·
#7648
·
|
|
Peer communication during chaincode execution
Dear all,
I wonder is it possible for peers to pass message to each other on the channel during the chaincode execution in the context of chaincode developer level not the protocol level? Or we need
Dear all,
I wonder is it possible for peers to pass message to each other on the channel during the chaincode execution in the context of chaincode developer level not the protocol level? Or we need
|
By
Kimheng SOK
·
#7647
·
|
|
anyone able to iterate over records using getStateByRange?
this method:
https://fabric-shim.github.io/master/fabric-shim.ChaincodeStub.html#getStateByRange
Note that startKey and endKey can be empty string, which implies unbounded range query on start or
this method:
https://fabric-shim.github.io/master/fabric-shim.ChaincodeStub.html#getStateByRange
Note that startKey and endKey can be empty string, which implies unbounded range query on start or
|
By
Siddharth Jain
·
#7646
·
|
|
Peer crash due to error during block commit
#fabric
#couchdb
Error:
Got error while committing(read tcp 10.0.9.49:37944->10.0.9.15:5984: read: connection reset by peer
error reading response body
We have the following environment setup and
Error:
Got error while committing(read tcp 10.0.9.49:37944->10.0.9.15:5984: read: connection reset by peer
error reading response body
We have the following environment setup and
|
By
Faisal
·
#7645
·
|
|
Re: Error: could not assemble transaction: ProposalResponsePayloads do not match
I got this error often, the reason is all the peer node execute their own chaincode individually and even if the result is successful, it doesn't means that all the payload are the same. By looking at
I got this error often, the reason is all the peer node execute their own chaincode individually and even if the result is successful, it doesn't means that all the payload are the same. By looking at
|
By
Kimheng SOK
·
#7644
·
|
|
Re: CORE_PEER_CHAINCODEADDRESS when peer is not running in a docker container
Whatever public IP other peers would use to connect to it. Docker and NAT (in docker's case double or triple NAT) complicate matters, you will have to pay attention to how you will have peers
Whatever public IP other peers would use to connect to it. Docker and NAT (in docker's case double or triple NAT) complicate matters, you will have to pay attention to how you will have peers
|
By
Nye Liu <nye@...>
·
#7643
·
|
|
CORE_PEER_CHAINCODEADDRESS when peer is not running in a docker container
What should be the CORE_PEER_CHAINCODEADDRESS when the peer is not running in a docker container? E.g., peer is running on the host and listening for chaincode at 0.0.0.0:7052. If we set
What should be the CORE_PEER_CHAINCODEADDRESS when the peer is not running in a docker container? E.g., peer is running on the host and listening for chaincode at 0.0.0.0:7052. If we set
|
By
Siddharth Jain
·
#7642
·
|
|
Re: Error: could not assemble transaction: ProposalResponsePayloads do not match
could anyone point us to the code where the response payload is generated? is there any doc explaining what the response payload is? its a byte array but what does it contain?
From: Siddharth Jain
could anyone point us to the code where the response payload is generated? is there any doc explaining what the response payload is? its a byte array but what does it contain?
From: Siddharth Jain
|
By
Siddharth Jain
·
#7641
·
|
|
Re: Storing/Retrieving key values in a collaborative way - endorsement policy
Your question gets to the heart of many use cases. And with v2.0 release coming, this is a great time to have the discussion. You have two options to choose from depending on your specific
Your question gets to the heart of many use cases. And with v2.0 release coming, this is a great time to have the discussion. You have two options to choose from depending on your specific
|
By
David Enyeart
·
#7640
·
|
|
Storing/Retrieving key values in a collaborative way - endorsement policy
Hello Fabric guys,
I have a scenario where there are X orgs in a Hyperledger Fabric network.
I would like to have each org can create/set/reset their respective values for key(s).
However, other orgs
Hello Fabric guys,
I have a scenario where there are X orgs in a Hyperledger Fabric network.
I would like to have each org can create/set/reset their respective values for key(s).
However, other orgs
|
By
Anoop Vijayan <anoop@...>
·
#7639
·
|
|
Error: could not assemble transaction: ProposalResponsePayloads do not match
we get this error when trying to invoke the chaincode on a network of 3 peers. However, we have verified if we invoke the chaincode individually on the peer nodes, all of them respond with Chaincode
we get this error when trying to invoke the chaincode on a network of 3 peers. However, we have verified if we invoke the chaincode individually on the peer nodes, all of them respond with Chaincode
|
By
Siddharth Jain
·
#7638
·
|
|
signature set did not satisfy policy
#fabric
#fabric-questions
I've created a network configuration with 2 orgs, each one with 1 peer and CA.
I've successfully installed and instantiated my chaincode on both peers
But after invoking a transaction this error
I've created a network configuration with 2 orgs, each one with 1 peer and CA.
I've successfully installed and instantiated my chaincode on both peers
But after invoking a transaction this error
|
By
George
·
#7637
·
|
|
revive^CC: static analysis of Go smart contracts
Has anyone taken a look at revive^CC? it is:
Static analysis tool for Hyperledger Fabric smart contracts written in Go.
Ry--
Ry Jones
Community Architect, Hyperledger
Chat: @rjones
Has anyone taken a look at revive^CC? it is:
Static analysis tool for Hyperledger Fabric smart contracts written in Go.
Ry--
Ry Jones
Community Architect, Hyperledger
Chat: @rjones
|
By
Ry Jones
·
#7636
·
|
|
Re: CORE_PEER_ADDRESS vs CORE_PEER_LISTENADDRESS
Listen is for the bind() call. Peer address is the externally visible address published during discovery. Please research bind() if that is unclear.
Listen is for the bind() call. Peer address is the externally visible address published during discovery. Please research bind() if that is unclear.
|
By
Nye Liu <nye@...>
·
#7635
·
|
|
Re: CORE_PEER_ADDRESS vs CORE_PEER_LISTENADDRESS
One more question.
I am assuming the CORE_PEER_CHAINCODEADDRESS and CORE_PEER_CHAINCODELISTENADDRESS are analogous to CORE_PEER_ADDRESS and CORE_PEER_LISTENADDRESS respectively i.e.,
whereas the
One more question.
I am assuming the CORE_PEER_CHAINCODEADDRESS and CORE_PEER_CHAINCODELISTENADDRESS are analogous to CORE_PEER_ADDRESS and CORE_PEER_LISTENADDRESS respectively i.e.,
whereas the
|
By
Siddharth Jain
·
#7634
·
|
|
Re: CORE_PEER_ADDRESS vs CORE_PEER_LISTENADDRESS
What if your friend is abroad and you'recalling his office phone, and he configured his office phone to redirectthe call to his cellphone?
The listen address is the address thepeerbinds its socket. It
What if your friend is abroad and you'recalling his office phone, and he configured his office phone to redirectthe call to his cellphone?
The listen address is the address thepeerbinds its socket. It
|
By
Yacov
·
#7633
·
|