Date   

One of the orderers crashes after created the network using No-system-channel setup#channel

Howin Ho
 

Hi Experts,

I have setup a 5 orderers Raft network with Fabric v2.4.0-beta using the No-system-channel way (https://hlf.readthedocs.io/en/latest/create_channel/create_channel_participation.html) on kubernetes. I also add new peer nodes to the network after it is bootstrapped. It runs okay for the first hour or so and then one of the orderers gives me a CrashLoopBack with following errors. I tried it 2 times and it happens both times. Could you please shed some light on my problem? Many thanks!!

==============
│ 2021-08-27 13:55:55.615 HKT 0025 INFO [orderer.consensus.etcdraft] Step -> 2 [term: 1] received a MsgHeartbeat message with higher term from 4 [term: 3] channel=loanapp node=2                                                                                            │
│ 2021-08-27 13:55:55.615 HKT 0026 INFO [orderer.consensus.etcdraft] becomeFollower -> 2 became follower at term 3 channel=loanapp node=2                                                                                                                                    │
│ 2021-08-27 13:55:55.615 HKT 0027 PANI [orderer.consensus.etcdraft] commitTo -> tocommit(23) is out of range [lastIndex(0)]. Was the raft log corrupted, truncated, or lost? channel=loanapp node=2                                                                         │
│ panic: tocommit(23) is out of range [lastIndex(0)]. Was the raft log corrupted, truncated, or lost?                                                                                                                                                                        │
│ goroutine 116 [running]:                                                                                                                                                                                                                                                   │
│ go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc000656300, 0x0, 0x0, 0x0)                                                                                                                                                                                                 │
│     /go/src/github.com/hyperledger/fabric/vendor/go.uber.org/zap/zapcore/entry.go:234 +0x585                                                                                                                                                                               │
│ go.uber.org/zap.(*SugaredLogger).log(0xc0002078e0, 0xc000b3be04, 0x10f2d1b, 0x5d, 0xc000b48f00, 0x2, 0x2, 0x0, 0x0, 0x0)                                                                                                                                                   │
│     /go/src/github.com/hyperledger/fabric/vendor/go.uber.org/zap/sugar.go:234 +0xf6                                                                                                                                                                                        │
│ go.uber.org/zap.(*SugaredLogger).Panicf(...)                                                                                                                                                                                                                               │
│     /go/src/github.com/hyperledger/fabric/vendor/go.uber.org/zap/sugar.go:159                                                                                                                                                                                              │
│ github.com/hyperledger/fabric/common/flogging.(*FabricLogger).Panicf(0xc0002078e8, 0x10f2d1b, 0x5d, 0xc000b48f00, 0x2, 0x2)                                                                                                                                                │
│     /go/src/github.com/hyperledger/fabric/common/flogging/zap.go:74 +0x7c                                                                                                                                                                                                  │
│ go.etcd.io/etcd/raft.(*raftLog).commitTo(0xc00055cc40, 0x17)                                                                                                                                                                                                               │
│     /go/src/github.com/hyperledger/fabric/vendor/go.etcd.io/etcd/raft/log.go:203 +0x135                                                                                                                                                                                    │
│ go.etcd.io/etcd/raft.(*raft).handleHeartbeat(0xc000148640, 0x8, 0x2, 0x4, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, ...)                                                                                                                                                               │
│     /go/src/github.com/hyperledger/fabric/vendor/go.etcd.io/etcd/raft/raft.go:1324 +0x54                                                                                                                                                                                   │
│ go.etcd.io/etcd/raft.stepFollower(0xc000148640, 0x8, 0x2, 0x4, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, ...)                                                                                                                                                                          │
│     /go/src/github.com/hyperledger/fabric/vendor/go.etcd.io/etcd/raft/raft.go:1269 +0x439                                                                                                                                                                                  │
│ go.etcd.io/etcd/raft.(*raft).Step(0xc000148640, 0x8, 0x2, 0x4, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, ...)                                                                                                                                                                          │
│     /go/src/github.com/hyperledger/fabric/vendor/go.etcd.io/etcd/raft/raft.go:971 +0x1218                                                                                                                                                                                  │
│ go.etcd.io/etcd/raft.(*node).run(0xc0003e7140, 0xc000148640)                                                                                                                                                                                                               │
│     /go/src/github.com/hyperledger/fabric/vendor/go.etcd.io/etcd/raft/node.go:357 +0x1178                                                                                                                                                                                  │
│ created by go.etcd.io/etcd/raft.StartNode                                                                                                                                                                                                                                  │
│     /go/src/github.com/hyperledger/fabric/vendor/go.etcd.io/etcd/raft/node.go:233 +0x449 
==============


Can I get some infos like timestamp, hash, the ledger itself by running a command by terminal?

gavimath16@...
 

Hello, I'd like to know if there's a way to get some information just like timestamp, hashes, the ledger itself.... as I can view when integrating my network with Explorer?


Re: Hyperledger Fabric Operator

DAVID VIEJO POMATA
 

Hello Nikos,

We're using the hyperledger fabric operator without any problems so far, this includes peers and orderers distributed on multiple kubernetes clusters.

Regarding the guide, the operator uses the Fabric CA to enrol the identities for the Peer and Orderer, as well as to renew the certificates, which is a recent feature introduced in PR #16.

Best Regards.
David Viejo.
KFS


El jue, 26 ago 2021 a las 10:36, Nikos Karamolegkos (<nkaram@...>) escribió:
Hello, nice work. So can we use this implementation for production networks directly? I mean without any problems? Is this compatible with this guide?


Re: Hyperledger Fabric Operator

Nikos Karamolegkos
 

Hello, nice work. So can we use this implementation for production networks directly? I mean without any problems? Is this compatible with this guide?


Re: Can I view contracts in a chaincode?

gqqnb2005 <gqqnb2005@...>
 

In short, I need to use `peer chaincode query -C mychannel -n basic -c
'{"Args":["org.hyperledger.fabric:GetMetadata"]}'`

It works like a charm. Thanks so much!


deploying Multi ORG on multi hosts (2.1) #docker

ilyessv12@...
 

Hello everyone,
 
I am training on this example simple enough to deploy on two machines : https://www.rapidqube.com/hyperledger-fabric-2-0-on-multiple-hosts/
 
I'm trying to test it on two machines, I do everything, and when I run (createChannel.sh) I have this error:
 
Successfully submitted proposal to join channel
Error: error getting endorser client for channel: endorser client failed to connect to localhost: 9051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:9051: connect: connection refused"
Error: error getting endorser client for channel: endorser client failed to connect to localhost: 10051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:10051: connect: connection refused"
could someone tell me why? and how to correct this error?


Re: Error while invoking functions of the chaincode using Node SDK (Fabric network on Kubernetes) #fabric #kubernetes #fabric-sdk-node

Mark Lewis
 

Those certificate verification failures during the TLS handshake look like a problem to me. I guess the node certificates are not valid for localhost. Maybe you could add entries to your client's local hosts file so it resolves the node addresses (peer0.org1, ca.org1) to the localhost/loopback address and the discovery / as localhost option in your client to false, so the client thinks it is connecting to the address specified in the server certificates.


Re: Can I view contracts in a chaincode?

Mark Lewis
 

If you are using the Contract API for your chaincode / smart contract implementation, your chaincode should have a "org.hyperledger.fabric:GetMetadata" transaction function that will provide you with information on the smart contracts and transaction functions contained in the chaincode. See this Gist for details of how to retrieve the metadata using a client application, although you could also use the Fabric CLI:

https://gist.github.com/mbwhite/f335f2ec46ec7544fb0f386fb049029b#file-metadata-ts-L106-L121


Now: Private Chaincode Lab - 08/24/2021 #cal-notice

fabric@lists.hyperledger.org Calendar <noreply@...>
 

Private Chaincode Lab

When:
08/24/2021
8:00am to 9:00am
(UTC-07:00) America/Los Angeles

Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Organizer: Marcus Brandenburger bur@...

View Event

Description:
Two of the Hyperleger Labs projects (private data objects and private chain code) are collaborating to develop a "private smart contracts" capability.

Join Zoom Meeting https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Meeting ID: 518 494 7650 Passcode: 475869


Error while invoking functions of the chaincode using Node SDK (Fabric network on Kubernetes) #fabric #kubernetes #fabric-sdk-node

Pratik Sanjay Patil <pratikspatil024@...>
 

Hello, we are running a Hyperledger Fabric network on Kubernetes (using minikube, kubectl to run locally) and then trying to connect the Node SDK with the network.

Currently, we have a fabric network (version 2.2.0) on Kubernetes in 3 different namespaces org1, org2, and org3. We have a channel created and chaincode installed, approved, and committed. In org 1, we have admin, CA, peer, and an ordering node. And in org2 and org3 each, we have an ordering node.

Now, we want to create a Node SDK that can interact with the network to enroll admin, register users, and create transactions by calling functions of the chaincode. We can currently interact with the chaincode by executing the `peer chaincode invoke ......` command in the admin pod.

We are currently forwarding the port of the CA (from ca.org1:7054 to localhost:7054), and Peer (from peer0.org1:7051 to localhost:7051). We can create the identities, but could not interact with the chaincode (using the Node SDK).

Error while invoking the chaincode function:
E0823 11:03:02.958440051 1061610 ssl_transport_security.cc:1245] Handshake failed with fatal error SSL_ERROR_SSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed.
E0823 11:03:03.934503504 1061610 ssl_transport_security.cc:1245] Handshake failed with fatal error SSL_ERROR_SSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed.
E0823 11:03:05.435949717 1061610 ssl_transport_security.cc:1245] Handshake failed with fatal error SSL_ERROR_SSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed.
2021-08-23T05:33:05.899Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Endorser- name: peer0.org1, url:grpcs://localhost:7051
2021-08-23T05:33:05.901Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer0.org1 url:grpcs://localhost:7051 timeout:3000
2021-08-23T05:33:05.902Z - error: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer0.org1 due to Error: Failed to connect before the deadline on Endorser- name: peer0.org1, url:grpcs://localhost:7051
2021-08-23T05:33:05.942Z - error: [Transaction]: Error: No valid responses from any peers. Errors


Peer Logs:

2021-08-23 05:28:55.828 UTC [comm.grpc.server] 1 -> INFO 059 streaming call completed grpc.service=protos.Deliver grpc.method=DeliverFiltered grpc.request_deadline=2021-08-23T05:29:21.725Z grpc.peer_address=172.17.0.1:53918 error="context finished before block retrieved: context canceled" grpc.code=Unknown grpc.call_duration=4.101995252s
2021-08-23 05:33:02.958 UTC [core.comm] ServerHandshake -> ERRO 05a Server TLS handshake failed in 1.008546ms with error EOF server=PeerServer remoteaddress=127.0.0.1:54680
2021-08-23 05:33:03.935 UTC [core.comm] ServerHandshake -> ERRO 05b Server TLS handshake failed in 2.485895ms with error EOF server=PeerServer remoteaddress=127.0.0.1:54688
2021-08-23 05:33:05.436 UTC [core.comm] ServerHandshake -> ERRO 05c Server TLS handshake failed in 2.58832ms with error EOF server=PeerServer remoteaddress=127.0.0.1:54698


You can view the connection.json file here: https://pastebin.ubuntu.com/p/PbQfJdrkQ8/

Also, the output of `openssl x509 -noout -text -in ./crypto-config/peerOrganizations/org1/tlsca/tlsca.org1-cert.pem` (with SAN: localhost) is this:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            9c:80:64:40:68:62:6f:d3:39:2b:87:e7:83:b2:a2:56
        Signature Algorithm: ecdsa-with-SHA256
        Issuer: C = US, ST = California, L = San Francisco, O = org1, CN = tlsca.org1
        Validity
            Not Before: Aug 23 13:05:00 2021 GMT
            Not After : Aug 21 13:05:00 2031 GMT
        Subject: C = US, ST = California, L = San Francisco, O = org1, CN = tlsca.org1
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:81:08:9d:68:6e:2f:86:b1:28:40:5b:a6:63:cb:
                    31:fd:81:15:2a:ee:33:45:f6:7a:65:13:b1:65:c9:
                    df:2c:0f:c5:b0:4c:ed:c5:d6:2b:7f:ec:9e:6f:cc:
                    6c:cf:a0:24:e7:a5:7e:29:bb:8a:30:d8:83:34:88:
                    ea:27:49:9a:49
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign, CRL Sign
            X509v3 Extended Key Usage: 
                TLS Web Client Authentication, TLS Web Server Authentication
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier: 
                78:F8:35:37:B4:9A:95:90:90:BB:D8:ED:46:DF:B2:6E:C6:A5:8C:5B:81:58:98:59:54:95:69:7E:65:D8:CC:B2
    Signature Algorithm: ecdsa-with-SHA256
         30:44:02:20:22:0c:0b:99:f7:78:90:6c:22:8c:b1:0c:b4:c7:
         ec:6c:b3:83:95:14:73:b0:c6:b4:b1:dc:1c:71:43:9f:a5:f6:
         02:20:51:b0:50:1d:33:8b:38:e5:18:0e:85:2f:ed:27:b9:9c:
         3e:84:62:5e:42:8f:52:a2:e5:f1:a5:34:97:95:dd:56


Any help will be appriciated, Thank you.

 


External chaincode build - package couchdb indexes #fabric #couchdb

neeroz.kumar29@...
 

I am building and deploying the chaincode externally on hyperledger fabric v2.3.2 and using couchdb as the state DB. I would appreciate if anyone could tell me how to package the couch DB indexes?

CouchDB Index

I have tried few ways:
  • package the META-INF directory along with the connection.json which outputs "code.tar.gz" ---> this resulted in error during chaincode installtion (invalid file type)
  • package the META-INF directory along with "code.tar.gz" and "metadata.json" which outputs "cc_name.tgz" ----> this doesn't creates any indexes in couchDB or it gives the same error as above


Re: identity and tls certs expired in Hyperledger fabric #ssl #fabric

neeroz.kumar29@...
 

The below error might have been caused due to "system-channel" in which orderer is a participant. You might have created "system-channel" first and then an application channel "mychannel" using the genesis block. Seems like you updated the channel configuration "consenters" in "mychannel" but did not update the same in "system-channel".

2021-08-04 05:00:29.192 UTC [orderer.common.broadcast] ProcessMessage -> WARN d06 [channel: mychannel] Rejecting broadcast of message from 10.56.1.5:40874 with SERVICE_UNAVAILABLE: rejected by Consenter: channel mychannel is not serviced by me
This below error is due to the fact that "orderer" is a participant in "system-channel" but not in your application channel "mychannel". In the HLF version v2.3+ there's no need to create the "system-channel" and "consortium". Orderers and peers can join multiple channel using "osnadmin" cli and when it comes to updating the certificates only the application channel "mychannel" needs to be updated.

2021-08-04 10:38:18.424 IST [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2021-08-04 10:38:18.804 IST [cli.common] readBlock -> INFO 002 Expect block, but got status: &{SERVICE_UNAVAILABLE}
Error: can't read the block: &{SERVICE_UNAVAILABLE}
You can try to restore the old certificates (i hope you had taken a backup of the crypto materials) and restart the fabric network, and create the "system-channel" and application channel once again. 


Can I view contracts in a chaincode?

gqqnb2005 <gqqnb2005@...>
 

I'm able to follow
https://hyperledger-fabric.readthedocs.io/en/release-2.2/test_network.html

Now I'm at this step

Run the following command to initialize the ledger with assets:

peer chaincode invoke -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n basic --peerAddresses localhost:7051 --tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses localhost:9051 --tlsRootCertFiles ${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c '{"function":"InitLedger","Args":[]}'
-> INFO 001 Chaincode invoke successful. result: status:200

Since I've deployed the basic chaincode, is there a command line tool
available for inspecting the chaincode and seeing what contracts are
there?

I know the basic example is open source, but can the command line tell
me more about the deployed chaincode without accessing the source
code?


Re: Re. Static or Dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java Contract APIs #fabric-chaincode

Baohua Yang
 

This one focuses on Go chaincode: https://github.com/sivachokkapu/revive-cc.


On Mon, Aug 23, 2021 at 4:48 AM Marcos Sarres <marcos.sarres@...> wrote:

I have used Sonar Qube in the past , but had few results, just some semantic and syntax tips.

 

Regards,

 

Marcos Sarres | CEO | +55 61 98116 7866

 

 

De: fabric@... <fabric@...> Em nome de Bharg Pvr
Enviada em: domingo, 22 de agosto de 2021 21:46
Para: fabric@...
Assunto: [Hyperledger Fabric] Re. Static or Dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java Contract APIs #fabric-chaincode

 

Dear team,

I am trying to find and put to use - static and/or dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java language Contract APIs with current versions of HLF chaincode programs [v2.3.2, v2.2.x and Beta v2.4.0].

Can you please point me to anything anyone may know? and I would gratefully forward thank for your help.

Best wishes.



--
Best wishes!

Baohua Yang


Re: Re. Static or Dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java Contract APIs #fabric-chaincode

Marcos Sarres
 

I have used Sonar Qube in the past , but had few results, just some semantic and syntax tips.

 

Regards,

 

Marcos Sarres | CEO | +55 61 98116 7866

 

 

De: fabric@... <fabric@...> Em nome de Bharg Pvr
Enviada em: domingo, 22 de agosto de 2021 21:46
Para: fabric@...
Assunto: [Hyperledger Fabric] Re. Static or Dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java Contract APIs #fabric-chaincode

 

Dear team,

I am trying to find and put to use - static and/or dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java language Contract APIs with current versions of HLF chaincode programs [v2.3.2, v2.2.x and Beta v2.4.0].

Can you please point me to anything anyone may know? and I would gratefully forward thank for your help.

Best wishes.


Re: Adding new channels to an existing network

Nikos Karamolegkos
 

I have a question related to this topic. When should I create a new channel and when should I create an entire new network? For example, let's say that there is a network with N organizations in one channel. If M other organizations want to create a consortium in a entire different channel should I create a new network or a new channel with this M organization. I will use HLF 2.2


Re. Static or Dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java Contract APIs #fabric-chaincode

Bharg Pvr <pvrbharg@...>
 

Dear team,

I am trying to find and put to use - static and/or dynamic security and vulnerability scanning tools for smart contracts - Go, Node.js and Java language Contract APIs with current versions of HLF chaincode programs [v2.3.2, v2.2.x and Beta v2.4.0].

Can you please point me to anything anyone may know? and I would gratefully forward thank for your help.

Best wishes.


Re: 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021

David Enyeart
 

Yeah, if it is possible to block new issues for all Fabric projects, but allow edits on existing issues, that would be ideal. Is it possible to add a banner re-directing people to GitHub issues?
I will update all the references to Jira in the fabric repo, including the ReadTheDocs references.
For prioritized issues, we plan to close them in Jira and open in GitHub. People with open issues in Jira can also do this themselves.


Dave Enyeart
IBM Blockchain
enyeart@...


"Ry Jones" ---08/20/2021 11:28:55 AM---Should I mark Jira read-only for new issues? On Fri, Aug 20, 2021 at 8:01 AM David Enyeart <enyeart@

From: "Ry Jones" <rjones@...>
To: "David Enyeart" <enyeart@...>
Cc: "david liu" <david-khala@...>, "fabric" <fabric@...>
Date: 08/20/2021 11:28 AM
Subject: [EXTERNAL] Re: 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021





Should I mark Jira read-only for new issues? On Fri, Aug 20, 2021 at 8:01 AM David Enyeart <enyeart@...> wrote: There are a few Gateway discussions ongoing. Feel free to continue those discussions if the topic is relevant, or start ZjQcmQRYFpfptBannerStart 
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Should I mark Jira read-only for new issues?

On Fri, Aug 20, 2021 at 8:01 AM David Enyeart <enyeart@...> wrote:
    There are a few Gateway discussions ongoing. Feel free to continue those discussions if the topic is relevant, or start new discussion topics at https://github.com/hyperledger/fabric-gateway/discussions.

    Note that we have enabled GitHub Issues and GitHub Discussions on all hyperledger/fabric-* repositories.


    Dave Enyeart



    "david liu" ---08/19/2021 01:06:52 PM---Hi Dave, Which Github discussion thread should we use to continue on event capability of Gateway SDK

    From:
    "david liu" <david-khala@...>
    To:
    "David Enyeart" <enyeart@...>
    Cc:
    "fabric" <fabric@...>
    Date:
    08/19/2021 01:06 PM
    Subject:
    [EXTERNAL] 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021
    Sent by:
    fabric@...




    Hi Dave, Which Github discussion thread should we use to continue on event capability of Gateway SDK? And BTW, + 1 for GitHub discussion and GitHub issue adoption in Fabric community. ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ZjQcmQRYFpfptBannerStart
     
    This Message Is From an External Sender

    This message came from outside your organization.

    ZjQcmQRYFpfptBannerEnd

    Hi Dave,
     
    Which Github discussion thread should we use to continue on event capability of Gateway SDK?
     
    And BTW, + 1 for
    GitHub discussion and GitHub issue adoption in Fabric community.
     

    发件人: fabric@... <fabric@...> 代表 David Enyeart <enyeart@...>
    发送时间
    : 2021819 5:09
    收件人
    : David Enyeart <enyeart@...>
    抄送
    : fabric <fabric@...>
    主题
    : Re: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021 
     

    The new Fabric Gateway SDK event listening capabilities were discussed on the contributor call today. As mentioned during the meeting, we welcome any feedback, especially from users that are currently using or evaluating the event capabilities in existing Fabric SDKs.
    Feedback can be provided on this mailing list or in the GitHub discussion forum:
    https://github.com/hyperledger/fabric-gateway/discussions.

    We also mentioned in the meeting that we are trying out the GitHub discussion and GitHub issue (as a replacement for Jira) features. If you have experience with these features we'd also like to hear about any good practices that have worked well.

    You can try out the Fabric Gateway and new SDKs by looking at the fabric-gateway v2.4.0-beta and samples:
    https://github.com/hyperledger/fabric-gateway/tree/main/samples.

    For more details, listen to the meeting replay:
    https://wiki.hyperledger.org/download/attachments/41590443/20210818_contributors_meeting.mp4?api=v2



    "David Enyeart" ---08/18/2021 08:29:15 AM---Today's agenda:   Fabric Gateway Event listening - Mark Lewis

    From:
    "David Enyeart" <enyeart@...>
    To:
    "fabric" <fabric@...>
    Date:
    08/18/2021 08:29 AM
    Subject:
    [EXTERNAL] [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021
    Sent by:
    fabric@...






    Today's agenda: Fabric Gateway Event listening - Mark Lewis If you have other topics, please attend the meeting today! ------------------------------------------------------------------------- Hyperledger Fabric Contributor Meeting When: ‍ZjQcmQRYFpfptBannerStart
     
    This Message Is From an External Sender

    This message came from outside your organization.

    ZjQcmQRYFpfptBannerEnd
     

    Today's agenda:
    Fabric Gateway Event listening - Mark Lewis

    If you have other topics, please attend the meeting today!


    -------------------------------------------------------------------------

    Hyperledger Fabric Contributor Meeting

    When: Every other Wednesday 9am US Eastern, 13:00 UTC (during US daylight savings time)

    Where: https ://zoom.us/j/51849 47650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

    Agendas and Recordings: https://wiki.hyperledger.org/display/fabric/Contributor+Meetings










--
Ry Jones
Community Architect, Hyperledger
Chat@rjones Calendar




Re: 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021

Ry Jones
 

Should I mark Jira read-only for new issues?


On Fri, Aug 20, 2021 at 8:01 AM David Enyeart <enyeart@...> wrote:

There are a few Gateway discussions ongoing. Feel free to continue those discussions if the topic is relevant, or start new discussion topics at https://github.com/hyperledger/fabric-gateway/discussions.

Note that we have enabled GitHub Issues and GitHub Discussions on all hyperledger/fabric-* repositories.


Dave Enyeart


"david liu" ---08/19/2021 01:06:52 PM---Hi Dave, Which Github discussion thread should we use to continue on event capability of Gateway SDK

From: "david liu" <david-khala@...>
To: "David Enyeart" <enyeart@...>
Cc: "fabric" <fabric@...>
Date: 08/19/2021 01:06 PM
Subject: [EXTERNAL] 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021
Sent by: fabric@...





Hi Dave, Which Github discussion thread should we use to continue on event capability of Gateway SDK? And BTW, + 1 for GitHub discussion and GitHub issue adoption in Fabric community. ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ZjQcmQRYFpfptBannerStart 
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hi Dave,
 
Which Github discussion thread should we use to continue on event capability of Gateway SDK?
 
And BTW, + 1 for GitHub discussion and GitHub issue adoption in Fabric community.
 

发件人: fabric@... <fabric@...> 代表 David Enyeart <enyeart@...>
发送时间
: 2021819 5:09
收件人
: David Enyeart <enyeart@...>
抄送
: fabric <fabric@...>
主题
: Re: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021 
 

The new Fabric Gateway SDK event listening capabilities were discussed on the contributor call today. As mentioned during the meeting, we welcome any feedback, especially from users that are currently using or evaluating the event capabilities in existing Fabric SDKs.
Feedback can be provided on this mailing list or in the GitHub discussion forum:
https://github.com/hyperledger/fabric-gateway/discussions.

We also mentioned in the meeting that we are trying out the GitHub discussion and GitHub issue (as a replacement for Jira) features. If you have experience with these features we'd also like to hear about any good practices that have worked well.

You can try out the Fabric Gateway and new SDKs by looking at the fabric-gateway v2.4.0-beta and samples:
https://github.com/hyperledger/fabric-gateway/tree/main/samples.

For more details, listen to the meeting replay:
https://wiki.hyperledger.org/download/attachments/41590443/20210818_contributors_meeting.mp4?api=v2



"David Enyeart" ---08/18/2021 08:29:15 AM---Today's agenda:   Fabric Gateway Event listening - Mark Lewis

From:
"David Enyeart" <enyeart@...>
To:
"fabric" <fabric@...>
Date:
08/18/2021 08:29 AM
Subject:
[EXTERNAL] [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021
Sent by:
fabric@...






Today's agenda: Fabric Gateway Event listening - Mark Lewis If you have other topics, please attend the meeting today! ------------------------------------------------------------------------- Hyperledger Fabric Contributor Meeting When: ‍ZjQcmQRYFpfptBannerStart
 
This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd
 

Today's agenda:
Fabric Gateway Event listening - Mark Lewis

If you have other topics, please attend the meeting today!


-------------------------------------------------------------------------

Hyperledger Fabric Contributor Meeting

When: Every other Wednesday 9am US Eastern, 13:00 UTC (during US daylight savings time)

Where: https ://zoom.us/j/51849 47650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Agendas and Recordings: https://wiki.hyperledger.org/display/fabric/Contributor+Meetings











--
Ry Jones
Community Architect, Hyperledger


Re: 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021

David Enyeart
 

There are a few Gateway discussions ongoing. Feel free to continue those discussions if the topic is relevant, or start new discussion topics at https://github.com/hyperledger/fabric-gateway/discussions.

Note that we have enabled GitHub Issues and GitHub Discussions on all hyperledger/fabric-* repositories.


Dave Enyeart


"david liu" ---08/19/2021 01:06:52 PM---Hi Dave, Which Github discussion thread should we use to continue on event capability of Gateway SDK

From: "david liu" <david-khala@...>
To: "David Enyeart" <enyeart@...>
Cc: "fabric" <fabric@...>
Date: 08/19/2021 01:06 PM
Subject: [EXTERNAL] 回复: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021
Sent by: fabric@...





Hi Dave, Which Github discussion thread should we use to continue on event capability of Gateway SDK? And BTW, + 1 for GitHub discussion and GitHub issue adoption in Fabric community. ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ZjQcmQRYFpfptBannerStart 
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hi Dave,
 
Which Github discussion thread should we use to continue on event capability of Gateway SDK?
 
And BTW, + 1 for GitHub discussion and GitHub issue adoption in Fabric community.
 

发件人: fabric@... <fabric@...> 代表 David Enyeart <enyeart@...>
发送时间
: 2021819 5:09
收件人
: David Enyeart <enyeart@...>
抄送
: fabric <fabric@...>
主题
: Re: [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021 
 

The new Fabric Gateway SDK event listening capabilities were discussed on the contributor call today. As mentioned during the meeting, we welcome any feedback, especially from users that are currently using or evaluating the event capabilities in existing Fabric SDKs.
Feedback can be provided on this mailing list or in the GitHub discussion forum:
https://github.com/hyperledger/fabric-gateway/discussions.

We also mentioned in the meeting that we are trying out the GitHub discussion and GitHub issue (as a replacement for Jira) features. If you have experience with these features we'd also like to hear about any good practices that have worked well.

You can try out the Fabric Gateway and new SDKs by looking at the fabric-gateway v2.4.0-beta and samples:
https://github.com/hyperledger/fabric-gateway/tree/main/samples.

For more details, listen to the meeting replay:
https://wiki.hyperledger.org/download/attachments/41590443/20210818_contributors_meeting.mp4?api=v2



"David Enyeart" ---08/18/2021 08:29:15 AM---Today's agenda:   Fabric Gateway Event listening - Mark Lewis

From:
"David Enyeart" <enyeart@...>
To:
"fabric" <fabric@...>
Date:
08/18/2021 08:29 AM
Subject:
[EXTERNAL] [Hyperledger Fabric] Fabric contributor meeting - August 18, 2021
Sent by:
fabric@...






Today's agenda: Fabric Gateway Event listening - Mark Lewis If you have other topics, please attend the meeting today! ------------------------------------------------------------------------- Hyperledger Fabric Contributor Meeting When: ‍ZjQcmQRYFpfptBannerStart
 
This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd
 

Today's agenda:
Fabric Gateway Event listening - Mark Lewis

If you have other topics, please attend the meeting today!


-------------------------------------------------------------------------

Hyperledger Fabric Contributor Meeting

When: Every other Wednesday 9am US Eastern, 13:00 UTC (during US daylight savings time)

Where: https ://zoom.us/j/51849 47650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Agendas and Recordings: https://wiki.hyperledger.org/display/fabric/Contributor+Meetings









1201 - 1220 of 11409