Summary
- How to fix all the bot pull requests
- Methane project
- Harsh mentorship wrap up. Outstanding issues:
- OrbitDB refactoring
- Using OrbitDB in Fabric docker containers, which requires Node 16
Steps taken so far to try and get OrbitDB to run with chaincode:
- Upgraded Fabric version to v2.4.3 (latest release at the time of writing) because it supports running Node v16 in the chaincode environment
- Set the CORE_CHAINCODE_NODE_RUNTIME environment variable to "hyperledger/fabric-nodeenv:2.4.1" (as mentioned in the compatibility docs for fabric-chaincode-node). However, on trying to print out the value of this environment variable in the container itself (using
echo $CORE_CHAINCODE_NODE_RUNTIME), there is no output (i.e. this variable is not being set, despite being in the YAML configuration.) - Created a new Dockerfile for compiling chaincode from TS into JS, using Node v16, and built and used this image for compilation (this is working as expected, and the chaincode is being compiled correctly).
Time:
- Monday at 09 AM Pacific
- Add Climate Action and Accounting SIG calls to your calendar
Dial-In Information: [ZOOM]
You can join either from your computer or from your phone:
- From computer: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
- From phone: +1(855)880-1246 (toll free US number) or view International numbers
Meeting ID: 622 333 6701
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
