Provide clear guidance for debugging Java chaincode as a service #684 #724
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…incode as a service with a local debugger. Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
|
cc: @timo-kang @jt-nti |
jt-nti
suggested changes
Apr 25, 2022
.../chaincode-java/src/main/java/org/hyperledger/fabric/samples/assettransfer/ContractMain.java
Outdated
Show resolved
Hide resolved
mbwhite
reviewed
Apr 26, 2022
| network cc invoke asset-transfer-debug '{"Args":["InitLedger"]}' | ||
| network cc query asset-transfer-debug '{"Args":["ReadAsset","asset1"]}' | ||
| ``` | ||
|
|
There was a problem hiding this comment.
Worth highlighting the connection timeout ? That when stepping through the code you need to be mindful of the transaction timingout.
.../chaincode-java/src/main/java/org/hyperledger/fabric/samples/assettransfer/ContractMain.java
Outdated
Show resolved
Hide resolved
| function absolute_path() { | ||
| local relative_path=$1 | ||
|
|
||
| local abspath="$( cd "${relative_path}" && pwd )" |
There was a problem hiding this comment.
think the 'realpath' command will do this for you.
There was a problem hiding this comment.
it would.
If you "just run Linux."
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
|
/azp run Lint failed in a typescript routine from this PR? Wut? |
|
No pipelines are associated with this pull request. |
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
READY FOR MERGE
(This PR replaces PR #684, which lingered for too long in a DRAFT / review status, spanned multiple approaches, and had merge conflicts with the mainline.)
This PR addresses the need for a simple, clear example that illustrates the use of Chaincode-as-a-Service to build and run Java chaincode on a local development environment.
In addition, the README includes a section that describes how users may employ a Docker loopback interface to connect from a remote Peer binary to a local port on the host OS. In this manner, chaincode may be run locally while attached to a debugger, with the peer running on a remote pod in Kubernetes.
In the first iteration of this PR, we introduced a new
ccpackage/*folder to hold descriptive files that would be used to generate the chaincode-as-a-service package, AND help with the deployment to k8s:After community review, the PR has been reflected to remove the /ccpackage/ folder, opting to dynamically construct the cc package based on conventions and additional CLI arguments. This has the benefit of applying directly to most (if not all) of the current sample code base, without introducing the crufty "ccaas" deployment descriptors for yet-another-deployment-technique-for-fabric.
A multi-phase Azure pipeline has been included to verify the overall approach for both golang and Java CCaaS asset transfer chaincode samples.
Some additional / loose ends that may warrant future PRs and improvements:
Additional testing on the
host.docker.internalDNS alias is required (e.g. Win, Linux, revs of Docker, etc.)The doc sets up a flow with three installations of the same chaincode, but does not delete the chaincode between steps. (How does one delete a chaincode, btw?)
file-based arguments must all be absolute paths.