-
Notifications
You must be signed in to change notification settings - Fork 404
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
can't catch the error of commitTimeOut , because of the unit is not uniform #1141
Comments
@workhard-12 Could you elaborate a bit, please? Which connector, which version/API? |
packages\caliper-fabric\lib\connector-versions\v2\FabricGateway.js
|
This is mainly a documentation issue as internally the code actually considers this to be seconds not milliseconds, however the default value of 60000 is assuming to be 60 seconds so the default value should change |
documentation part to hyperledger#1141 Signed-off-by: D <d_kelsey@uk.ibm.com>
This is the apparent cause of a caliper run hang where it continues to run with unfinished txns. It's actually waiting 60,000 seconds for txns to finish which won't finish as it looks like the node sdk misses the events. code part of hyperledger#1141 also addresses in part Signed-off-by: D <d_kelsey@uk.ibm.com>
documentation part to #1141 Signed-off-by: D <d_kelsey@uk.ibm.com> Co-authored-by: D <d_kelsey@uk.ibm.com>
This is the apparent cause of a caliper run hang where it continues to run with unfinished txns. It's actually waiting 60,000 seconds for txns to finish which won't finish as it looks like the node sdk misses the events. code part of #1141 also addresses in part Signed-off-by: D <d_kelsey@uk.ibm.com> Co-authored-by: D <d_kelsey@uk.ibm.com>
Docs have been updated and code base has changed the default from 60,000 to 60. In the mean time you can override the default with
when you launch caliper |
When we submit a tx , the unit of "commitTimeOut" should be seconds , but the caliper use milliseconds.
The text was updated successfully, but these errors were encountered: