-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Refactor extendChaincodesConfig.ts to allow private data in chaincode #460
chore: Refactor extendChaincodesConfig.ts to allow private data in chaincode #460
Conversation
…aincode Signed-off-by: Akash Singh <[email protected]>
Thanks, I've approved the CI run and we'll see how it goes. I'm 90% sure you'll need to also update snapshots locally (see: https://github.com/hyperledger-labs/fablo/blob/main/CONTRIBUTING.md#making-changes), but after that it will be good to go. |
@dzikowski I am having some problems in updating the snapshot.
|
Are you sure it never ends? It should take a lot of time, even a couple of minutes. And eventually, if there is an error with Fablo, the test engine (Jest) should terminate the test with an error. |
@Akash-Singh04 After merging changes from main branch everything seems working. Approving and merging. |
References
Issue Details
The default configuration for
requiredPeerCount
causes the following error:Solution
The solution is to allow
requiredPeerCount
to be set to 0. This can be achieved by modifying the logic in the code that generates this property. Specifically, removing the|| 1
part from the following lines of code:Changes Made
|| 1
from the calculation ofrequiredPeerCount
to allow it to be set to 0 if necessary.