-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FAB-5921] add channel to proposal contexts
Proposal contexts are currently keyed of just transaction IDs. This prevents CC-2-CC calls where the called CC is on a different channel (we want to use the same TXID for the entire CC call chain). This CR adds Channel ID to the context key. In addition to fixing the above bug, this also has a couple of good side effects . Chaincode can now get the ChannelID of proposals (they could do it from the proposal header but that would not work when calling a CC on a different channel) . proposals with the SAME transaction id can now be sent to the SAME chaincode on multiple channels (this is different from the CC-2-CC issue the bug was raised on) . patch-2 removed a check that should never have been there (forgot to remove it in previous checkin). Also found a bug that prevented that from kicking in. . patch-4 rebuilt protos to pick up protos/common/collection.pb.go (hopefully will fix z built UT failures in protos/utils) . patch-5 rebase and fix some "go vet" issues now that we are using go vet Change-Id: I7e4333d4219a0927885ed787fda05e0dcaab25fd Signed-off-by: Srinivasan Muralidharan <srinivasan.muralidharan99@gmail.com>
- Loading branch information
1 parent
25ce382
commit 92ca115
Showing
14 changed files
with
449 additions
and
319 deletions.
There are no files selected for viewing
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
Oops, something went wrong.