|
回复: missing tags for go chaincode developement dependencies
We have chosen not to add version tags to the modules because they tend to evolve compatibly and are mostly disconnected from the fabric releases. For example, if you pull any version of fabric-chainc
We have chosen not to add version tags to the modules because they tend to evolve compatibly and are mostly disconnected from the fabric releases. For example, if you pull any version of fabric-chainc
|
By
Matthew Sykes
· #9972
·
|
|
using go routine in the chaincode
#fabric-chaincode
#fabric-questions
It's less about a race and more about consistency. (A race can cause an inconsistency.) Imagine that when you run the contract on peer one, the sequence observed by the ledger is ["data1", "data2"]; o
It's less about a race and more about consistency. (A race can cause an inconsistency.) Imagine that when you run the contract on peer one, the sequence observed by the ledger is ["data1", "data2"]; o
|
By
Matthew Sykes
· #9871
·
|
|
Problematic raspberry support
You'll need to build with "GO_TAGS=noplugin" to disable the plugins when building the docker images. Should be as simple as 'make clean-all docker native GO_TAGS=noplugin'. You can verify the peer bui
You'll need to build with "GO_TAGS=noplugin" to disable the plugins when building the docker images. Should be as simple as 'make clean-all docker native GO_TAGS=noplugin'. You can verify the peer bui
|
By
Matthew Sykes
· #9786
·
|
|
Problematic raspberry support
I had some time this morning so I played around with the peer image created on linux/aarch64 (linux/arm64). To get to the bottom of why the program was dying during initialization, I commented out all
I had some time this morning so I played around with the peer image created on linux/aarch64 (linux/arm64). To get to the bottom of why the program was dying during initialization, I commented out all
|
By
Matthew Sykes
· #9769
·
|
|
Problematic raspberry support
Yeah, they’re all my commits so I’m very familiar with them. The change you’re referencing this time was required to get through the link phase in the alpine containers but the binaries in the contain
Yeah, they’re all my commits so I’m very familiar with them. The change you’re referencing this time was required to get through the link phase in the alpine containers but the binaries in the contain
|
By
Matthew Sykes
· #9764
·
|
|
Problematic raspberry support
Nikos, the Fabric team doesn’t do anything to support Raspberry Pi. The commit you’re referencing enables _development_ of Fabric on the new arm64 based M1 macs using the code in the core Fabric tree.
Nikos, the Fabric team doesn’t do anything to support Raspberry Pi. The commit you’re referencing enables _development_ of Fabric on the new arm64 based M1 macs using the code in the core Fabric tree.
|
By
Matthew Sykes
· #9761
·
|
|
how to reference fabric 2.2 in application go.mod?
#fabric
#fabric-chaincode
As of v2 of Fabric, the packages we expect applications and chaincode to build and link against have been extracted to `hyperledger/fabric-chaincode-go` and `hyperledger/fabric-protos-go`. Fabric is n
As of v2 of Fabric, the packages we expect applications and chaincode to build and link against have been extracted to `hyperledger/fabric-chaincode-go` and `hyperledger/fabric-protos-go`. Fabric is n
|
By
Matthew Sykes
· #9503
·
|
|
Peer logs filled with TLS handshake error
#fabric
#tls
#ssl
#fabric-questions
EOF - End of File. It's likely indicating the other end of the connection has closed during the handshake, that a network error occurred, or that a record header with an incorrect length was received.
EOF - End of File. It's likely indicating the other end of the connection has closed during the handshake, that a network error occurred, or that a record header with an incorrect length was received.
|
By
Matthew Sykes
· #9478
·
|
|
JWT Authentication
#rfc
I have created a proposal for JWT based authentication that can be used with the channel participation API. The goal is enable the use of MSP identities on the API and remove the requirement for mutua
I have created a proposal for JWT based authentication that can be used with the channel participation API. The goal is enable the use of MSP identities on the API and remove the requirement for mutua
|
By
Matthew Sykes
· #9477
·
|
|
Adding external builder scripts execution logs to peer pod
#fabric-questions
#externalbuilders
#fabric
Standard error (and only standard error) is redirected from the external builder to the peer's logs. This is already done at info level. The logger is named `chaincode.externalbuilder.<builder-name>`
Standard error (and only standard error) is redirected from the external builder to the peer's logs. This is already done at info level. The logger is named `chaincode.externalbuilder.<builder-name>`
|
By
Matthew Sykes
· #9211
·
|
|
memory used by peer went up horribly
Fabric uses protocol buffers for messages and persistence and gRPC+protobuf for inter-process communication. When a proposal message is sent to the peer, several copies of the proposal message end up
Fabric uses protocol buffers for messages and persistence and gRPC+protobuf for inter-process communication. When a proposal message is sent to the peer, several copies of the proposal message end up
|
By
Matthew Sykes
· #9180
·
|
|
Need help in configuring TLS for chaincode server
Unfortunately, the traceback doesn't really shed any light on the situation as almost all errors invoking chaincode will show the same stack. Did you set 'tls_required' and 'client_auth_required' to t
Unfortunately, the traceback doesn't really shed any light on the situation as almost all errors invoking chaincode will show the same stack. Did you set 'tls_required' and 'client_auth_required' to t
|
By
Matthew Sykes
· #9051
·
|
|
Does peer monitor externally running chaincode?
The chaincode server is your server; it's completely up to you how you want to manage and monitor it. The peer surfaces metrics for chaincode that cover most invocation scenarios (server or client, ex
The chaincode server is your server; it's completely up to you how you want to manage and monitor it. The peer surfaces metrics for chaincode that cover most invocation scenarios (server or client, ex
|
By
Matthew Sykes
· #9041
·
|
|
Does peer monitor externally running chaincode?
The peer does not perform any health or liveness checks and only enables keep alive pings on the gRPC connection. The first time the chaincode is invoked, the peer creates a grpc connection, connects
The peer does not perform any health or liveness checks and only enables keep alive pings on the gRPC connection. The first time the chaincode is invoked, the peer creates a grpc connection, connects
|
By
Matthew Sykes
· #9026
·
|
|
Install Hyperledger Fabric in Raspberry Pi
#fabric
We don't publish images for ARM but it's very easy to build fabric from source. And yes, it is possible to run Fabric on a Pi but only on 64 bit systems as one of the crypto packages used in Fabric on
We don't publish images for ARM but it's very easy to build fabric from source. And yes, it is possible to run Fabric on a Pi but only on 64 bit systems as one of the crypto packages used in Fabric on
|
By
Matthew Sykes
· #8631
·
|
|
How to verify that a state in the couchdb matches a transaction in the blockchain?
#fabric-sdk-node
#database
#fabric-questions
The value is base64 encoded, not encrypted. The value is represented as bytes and base64 is how bytes are represented in JSON. Your value is decoded as: {"class":"aipay.payment","key":"\"0004_workstat
The value is base64 encoded, not encrypted. The value is represented as bytes and base64 is how bytes are represented in JSON. Your value is decoded as: {"class":"aipay.payment","key":"\"0004_workstat
|
By
Matthew Sykes
· #8464
·
|
|
what does clientAuthRequired do?
#ssl
When you want to prevent unauthenticated usage of the operations health check endpoint. The metrics and logspec endpoints always require client certificate authentication when TLS is enabled. https://
When you want to prevent unauthenticated usage of the operations health check endpoint. The metrics and logspec endpoints always require client certificate authentication when TLS is enabled. https://
|
By
Matthew Sykes
· #8403
·
|
|
Windows 10: Bug when installing chaincode using external builders
#externalbuilders
Windows is not a supported platform for running the peer node natively. While it may work, it is not tested. We do, however, generally support the cli. Within Fabric, we try very hard to keep the prod
Windows is not a supported platform for running the peer node natively. While it may work, it is not tested. We do, however, generally support the cli. Within Fabric, we try very hard to keep the prod
|
By
Matthew Sykes
· #8366
·
|
|
[FAB-17598] Improve the efficiency of viperutil.EnhancedExactUnmarshal
In my experience, Jira issues age more like a weathered parking lot than a fine wine.... The excessive times are most easily observed when running with the race detector enabled and this is how we run
In my experience, Jira issues age more like a weathered parking lot than a fine wine.... The excessive times are most easily observed when running with the race detector enabled and this is how we run
|
By
Matthew Sykes
· #8365
·
|
|
peer container is down constantly
It's likely a bug. The gossip code is sitting in a select where one case is receiving from an error channel and the other is receiving a message. [1] If, however, an error occurs when converting an en
It's likely a bug. The gossip code is sitting in a select where one case is receiving from an error channel and the other is receiving a message. [1] If, however, an error occurs when converting an en
|
By
Matthew Sykes
· #8042
·
|