You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2019. It is now read-only.
Hello, I got a timeout error and found the following in the deployment log:
Node.js report completed
/home/pipeline/.nvm/versions/node/v8.11.1/lib/node_modules/composer-cli/node_modules/fabric-client/lib/EventHub.js:308
if(self._stream) state = self._stream.call.channel_.getConnectivityState();
^
TypeError: Cannot read property 'getConnectivityState' of undefined
at ClientDuplexStream.<anonymous> (/home/pipeline/.nvm/versions/node/v8.11.1/lib/node_modules/composer-cli/node_modules/fabric-client/lib/EventHub.js:308:56)
at emitOne (events.js:116:13)
at ClientDuplexStream.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at ClientDuplexStream.Readable.push (_stream_readable.js:208:10)
at Object.onReceiveMessage (/home/pipeline/.nvm/versions/node/v8.11.1/lib/node_modules/composer-cli/node_modules/grpc/src/client_interceptors.js:1302:19)
at InterceptingListener.recvMessageWithContext (/home/pipeline/.nvm/versions/node/v8.11.1/lib/node_modules/composer-cli/node_modules/grpc/src/client_interceptors.js:629:19)
at /home/pipeline/.nvm/versions/node/v8.11.1/lib/node_modules/composer-cli/node_modules/grpc/src/client_interceptors.js:728:14
sleeping to retry runtime install```
The text was updated successfully, but these errors were encountered:
"Yes, this is due to a new version of grpc released 3 days ago (v1.11.0). The version is controlled by fabric-client and it takes the latest available. You need to delete the grpc module and reinstall it with npm install [email protected]. This will fix the issue. Going forward you may need to have grpc fixed at 1.9.1 in your package.json until Hyperledger resolve this issue.
Hello, I got a timeout error and found the following in the deployment log:
The text was updated successfully, but these errors were encountered: