Merge branch 'main' into test-gateway-ci

Author: dzikowski

.github/workflows/test-on-push.yml

@@ -243,3 +243,27 @@ jobs:
           path: |
             e2e-network/docker/test-06-v3-bft.sh.logs/*
             e2e-network/docker/test-06-v3-bft.sh.tmpdir/fablo-target/**/*
+  test-07-v2-peer-dev-mode:
+    needs: test-main
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+
+      - name: Build Fablo
+        run: |
+          shellcheck --version && \
+          yamllint -v && \
+          npm install && \
+          ./fablo-build.sh
+
+      - name: Test v2 peer dev mode
+        run: e2e-network/docker/test-07-v2-peer-dev-mode.sh
+
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: test-07-v2-peer-dev-mode-snapshot
+          path: |
+            e2e-network/docker/test-07-v2-peer-dev-mode.sh.logs/*
+            e2e-network/docker/test-07-v2-peer-dev-mode.sh.tmpdir/fablo-target/**/*

CHANGELOG.md

@@ -1,6 +1,6 @@
-## 2.3.0
-
-### Features
+## 2.3.0 
+* Support for running Java chaincode in development mode
+ [#553](https://github.com/hyperledger-labs/fablo/pull/553)
 * Hardcode fablo config inside init generator
   [#554](https://github.com/hyperledger-labs/fablo/pull/554)
 * Publish sample chaincode Docker image
@@ -10,7 +10,6 @@
 * Export network topology with Mermaid 
   [#565](https://github.com/hyperledger-labs/fablo/pull/565)
 
-
 ## 2.2.0
 
 ### Features

README.md

@@ -264,6 +264,8 @@ This feature allows hot reload of chaincode code and speeds up the development a
 Fablo will run peers in dev mode when `global.peerDevMode` is set to `true`.
 Note: in this case TLS has to be disabled, otherwise config validation fails.
 
+#### For Node.js Chaincode:
+
 The simplest way of trying Fablo with dev mode is as follows:
 
 1. Execute `fablo init node dev`.
@@ -278,7 +280,7 @@ The simplest way of trying Fablo with dev mode is as follows:
    ```
    Now, when you update the chaincode source code, it will be automatically refreshed on Hyperledger Fabric Network.
 
-Our sample chaincode definition contains some scripts for running chaincode in dev mode:
+The relevant scripts in `package.json` look like:
 
 ```json
   "scripts": {
@@ -288,13 +290,44 @@ Our sample chaincode definition contains some scripts for running chaincode in d
     ...
   },
 ```
-
-Worth considering:
+**Worth considering for Node.js chaincode:**
 * If you want chaincode to be running on multiple peers, you need to start it multiple times, specifying different `--peer.address`
 * In case of errors ensure you have the same `--chaincode-id-name` as `CC_PACKAGE_ID` in Fablo output.
 
 Feel free to update this scripts to adjust it to your chaincode definition.
 
+
+#### For Java Chaincode:
+
+To run Java chaincode in dev mode:
+
+1. Make sure your Fablo config has `global.peerDevMode` set to `true` and TLS disabled.
+
+2. Start the network with `fablo up`.
+
+3. Build and run the Java chaincode locally. As a sample you may use the chaincode from the Fablo source code from the `samples/chaincodes/java-chaincode` directory. Ensure a proper relative path is provided in Fablo config.
+   ```bash
+   cd samples/chaincodes/java-chaincode
+   ./run-dev.sh
+   ```
+
+   The `run-dev.sh` script will:
+   - Build the chaincode using Gradle's shadowJar task
+   - Automatically detect the peer's IP address from the Docker container
+   - Start the chaincode with debug logging enabled
+   - Connect to the peer at port 7051
+
+For local development and review:
+- The chaincode will run with the name `simple-asset:1.0`
+- Debug level logging is enabled via `CORE_CHAINCODE_LOGLEVEL=debug`
+- You can modify the Java code and rebuild/restart to see changes
+- The peer connection is automatically configured using the Docker container's IP
+
+**Worth considering for Java chaincode:**
+- If you want the chaincode running on multiple peers, start multiple instances with different `CORE_PEER_ADDRESS` values
+- Ensure `CORE_CHAINCODE_ID_NAME` matches the chaincode name and version in your Fablo config (for instance `chaincode1:0.0.1`)
+- The Java chaincode uses Gradle's ShadowJar plugin to package all dependencies into a single JAR file
+
 ## Channel scripts
 
 ### channel help

e2e-network/docker/test-07-v2-peer-dev-mode.sh

@@ -0,0 +1,78 @@
+#!/usr/bin/env bash
+
+set -e
+
+TEST_TMP="$(rm -rf "$0.tmpdir" && mkdir -p "$0.tmpdir" && (cd "$0.tmpdir" && pwd))"
+TEST_LOGS="$(mkdir -p "$0.logs" && (cd "$0.logs" && pwd))"
+FABLO_HOME="$TEST_TMP/../../.."
+
+export FABLO_HOME
+
+CONFIG="$FABLO_HOME/samples/fablo-config-hlf2-1org-1chaincode-peer-dev-mode.json"
+NODECHAINCODE="$FABLO_HOME/samples/chaincodes/chaincode-kv-node"
+
+networkUp() {
+  "$FABLO_HOME/fablo-build.sh"
+  (cd "$TEST_TMP" && "$FABLO_HOME/fablo.sh" up "$CONFIG")
+}
+
+dumpLogs() {
+  echo "Saving logs of $1 to $TEST_LOGS/$1.log"
+  mkdir -p "$TEST_LOGS"
+  docker logs "$1" >"$TEST_LOGS/$1.log" 2>&1
+}
+
+networkDown() {
+  sleep 2
+  (for name in $(docker ps --format '{{.Names}}'); do dumpLogs "$name"; done)
+  (cd "$TEST_TMP" && "$FABLO_HOME/fablo.sh" down)
+}
+
+waitForContainer() {
+  sh "$TEST_TMP/../wait-for-container.sh" "$1" "$2"
+}
+
+waitForChaincode() {
+  (cd "$TEST_TMP" && sh ../wait-for-chaincode.sh "$1" "$2" "$3" "$4")
+}
+
+expectInvoke() {
+  (cd "$TEST_TMP" && sh ../expect-invoke-cli.sh "$1" "$2" "$3" "$4" "$5" "$6")
+}
+
+expectCommand() {
+  sh "$TEST_TMP/../expect-command.sh" "$1" "$2"
+}
+
+trap networkDown EXIT
+trap 'networkDown ; echo "Test failed" ; exit 1' ERR SIGINT
+
+# start the network
+networkUp
+
+# check if all nodes are ready
+waitForContainer "orderer0.group1.orderer.example.com" "Beginning to serve requests"
+waitForContainer "db.ca.org1.example.com" "database system is ready to accept connections"
+waitForContainer "ca.org1.example.com" "Listening on http://0.0.0.0:7054"
+waitForContainer "couchdb.peer0.org1.example.com" "Apache CouchDB has started. Time to relax."
+waitForContainer "peer0.org1.example.com" "Joining gossip network of channel my-channel1 with 1 organizations"
+waitForChaincode "peer0.org1.example.com" "my-channel1" "chaincode1" "0.0.1"
+
+echo "All nodes are ready"
+echo "Starting chaincode in development mode..."
+# make sure nodemon is installed and Install if not
+if ! command -v nodemon &> /dev/null; then
+  echo "nodemon could not be found, installing..."
+  npm install -g nodemon
+else
+  echo "nodemon is already installed"
+fi
+# start the chaincode in development mode
+(cd "$NODECHAINCODE" && npm i && npm run start:watch) &
+
+sleep 5
+
+# Test simple chaincode
+expectInvoke "peer0.org1.example.com" "my-channel1" "chaincode1" \
+  '{"Args":["KVContract:put", "name", "Willy Wonka"]}' \
+  '{\"success\":\"OK\"}'