why change chaincode name and function name unsuccessfully? about tape HOT 7 CLOSED

please check your value carefully. :-)
ref CI
https://github.com/Hyperledger-TWGC/tape/runs/5888215910?check_suite_focus=true#step:5:889

https://github.com/Hyperledger-TWGC/tape/runs/5888216566?check_suite_focus=true#step:5:812

value assignment works.

from tape.

this issue been closed as sample in CI works for now. if you are able to reproduce it via CI by a PR. or the CI fails in coming schedule running, then it makes sense to reopen it.

from tape.

what mean about CI and PR?

from tape.

what mean about CI and PR?

continue integration and pull request....

from tape.

I use the instruct "./tape -c config.yaml -n 20"
I already make sure the chaincode is
./network.sh deployCC -ccn basic -ccv 1 -cci initLedger -ccl golang -ccp ../asset-transfer-basic/chaincode-go/
and the config.yaml is :

peer1: &peer1
addr: localhost:7051
tls_ca_cert: ../organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp/tlscacerts/tlsca.org1.example.com-cert.pem

peer2: &peer2
addr: localhost:9051
tls_ca_cert: ../organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp/tlscacerts/tlsca.org2.example.com-cert.pem

peer3: &peer3
addr: localhost:22051
tls_ca_cert: ../organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/msp/tlscacerts/tlsca.org3.example.com-cert.pem

peer4: &peer4
addr: localhost:21051
tls_ca_cert: ../organizations/peerOrganizations/org4.example.com/peers/peer0.org4.example.com/msp/tlscacerts/tlsca.org4.example.com-cert.pem

peer5: &peer5
addr: localhost:23051
tls_ca_cert: ../organizations/peerOrganizations/org5.example.com/peers/peer0.org5.example.com/msp/tlscacerts/tlsca.org5.example.com-cert.pem

peer6: &peer6
addr: localhost:24051
tls_ca_cert: ../organizations/peerOrganizations/org6.example.com/peers/peer0.org6.example.com/msp/tlscacerts/tlsca.org6.example.com-cert.pem

peer7: &peer7
addr: localhost:25051
tls_ca_cert: ../organizations/peerOrganizations/org7.example.com/peers/peer0.org7.example.com/msp/tlscacerts/tlsca.org7.example.com-cert.pem

peer3: &peer8
addr: localhost:26051
tls_ca_cert: ../organizations/peerOrganizations/org8.example.com/peers/peer0.org8.example.com/msp/tlscacerts/tlsca.org8.example.com-cert.pem

orderer1: &orderer1
addr: localhost:7050
tls_ca_cert: ../organizations/ordererOrganizations/example.com/msp/tlscacerts/tlsca.example.com-cert.pem

policyFile: ./test/andLogic.rego

endorsers:

• *peer1
• *peer2
• *peer3
• *peer4
• *peer5
• *peer6
• *peer7
• *peer8

committers:

• *peer1
• *peer2
• *peer3
• *peer4
• *peer5
• *peer6
• *peer7
• *peer8

commitThreshold: 8

orderer: *orderer1

channel: mychannel
chaincode: basic

args:

• CreateAsset
• randomString8
• randomString8
• randomNumber0_50
• randomString8
• randomNumber0_50

mspid: Org1MSP
private_key: ../organizations/peerOrganizations/org1.example.com/users/[email protected]/msp/keystore/priv_sk
sign_cert: ../organizations/peerOrganizations/org1.example.com/users/[email protected]/msp/signcerts/[email protected]

num_of_conn: 2
client_per_conn: 2

now return the error

time="2022-04-17T05:42:22-07:00" level=error msg="rpc error: code = Unavailable desc = closing transport due to: connection error: desc = "error reading from server: EOF", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: "too_many_pings""

from tape.

received prior goaway: code: ENHA

you'd better debugging your own network by yourself.

from tape.

I can invoke chaincode in cmd correctly.

from tape.