Add peer log message for failure to invoke chaincode #2339
Merged
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
When looking in peer log to troubleshoot chaincode invocations, there is currently no difference between a successful invocation and a failure to execute, they all look successful. This change adds a log Warning with error message for each failure to invoke. Signed-off-by: David Enyeart <enyeart@us.ibm.com>
yacovm
approved these changes
Feb 2, 2021
|
@Mergifyio backport release-2.3 |
|
@Mergifyio backport release-2.2 |
mergify bot
pushed a commit
that referenced
this pull request
Feb 2, 2021
When looking in peer log to troubleshoot chaincode invocations, there is currently no difference between a successful invocation and a failure to execute, they all look successful. This change adds a log Warning with error message for each failure to invoke. Signed-off-by: David Enyeart <enyeart@us.ibm.com> Co-authored-by: David Enyeart <denyeart@Davids-MBP.nc.rr.com> (cherry picked from commit 4e74441)
|
Command
|
mergify bot
pushed a commit
that referenced
this pull request
Feb 2, 2021
When looking in peer log to troubleshoot chaincode invocations, there is currently no difference between a successful invocation and a failure to execute, they all look successful. This change adds a log Warning with error message for each failure to invoke. Signed-off-by: David Enyeart <enyeart@us.ibm.com> Co-authored-by: David Enyeart <denyeart@Davids-MBP.nc.rr.com> (cherry picked from commit 4e74441)
|
Command
|
denyeart
added a commit
that referenced
this pull request
Feb 2, 2021
When looking in peer log to troubleshoot chaincode invocations, there is currently no difference between a successful invocation and a failure to execute, they all look successful. This change adds a log Warning with error message for each failure to invoke. Signed-off-by: David Enyeart <enyeart@us.ibm.com> Co-authored-by: David Enyeart <denyeart@Davids-MBP.nc.rr.com> (cherry picked from commit 4e74441)
denyeart
added a commit
that referenced
this pull request
Feb 2, 2021
When looking in peer log to troubleshoot chaincode invocations, there is currently no difference between a successful invocation and a failure to execute, they all look successful. This change adds a log Warning with error message for each failure to invoke. Signed-off-by: David Enyeart <enyeart@us.ibm.com> Co-authored-by: David Enyeart <denyeart@Davids-MBP.nc.rr.com> (cherry picked from commit 4e74441)
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.
When looking in peer log to troubleshoot chaincode invocations,
there is currently no difference between a successful
invocation and a failure to execute, they all get logged as a successful ProcessProposal call.
This change adds a log Warning with error message for each failure to invoke.
Signed-off-by: David Enyeart enyeart@us.ibm.com