Chat stream with peer cancelled or closed when starting chaincode

[hyperledger]

Chat stream with peer cancelled or closed when starting chaincode

[Burnaviour]

what does this means :Lock explicitly to 2.4.2 fabric node modules what's the name of m module in pakage.json file ?

[mbwhite]

@Burnaviour when a node module is install in a project, the version attached is represented as a semver

npm install --save chalk
cat packge.json
....
  "dependencies": {
    "chalk": "^5.2.0"
  }
...

The ^ is a semver prefix that indicates how npm should resolve this.. in this case it's any version starting at 5.2 up to but not including 6.0.0

By 'lock' I mean making the version '5.2.0' in this example... i.e. remove the semver prefix.

See https://docs.npmjs.com/about-semantic-versioning

https://jubianchi.github.io/semver-check/#/ is very useful to experiment and learn how it works

Will add

[Burnaviour]

 "dependencies": {
    "@grpc/grpc-js": "1.8.1",
    "fabric-contract-api": "2.4.2",
    "fabric-shim": "2.4.2"
  },    did this in both lock json and pakage json file 

[mbwhite]

It looks like there are new releases of the grpc-js library; we've yet to test those. However the version of grpc-js has been locked to the working version in the published node chaincode. Therefore if using the latest this should be seen by folks.

[mbwhite]

Going to close this now, as we've locked versions of the grpc-js code