Skip to content
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

Configurable timeout period for GrpcServicesError in NodeChannel #1276

Closed
Ivo-Yankov opened this issue Sep 27, 2022 · 0 comments · Fixed by #1354
Closed

Configurable timeout period for GrpcServicesError in NodeChannel #1276

Ivo-Yankov opened this issue Sep 27, 2022 · 0 comments · Fixed by #1354
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@Ivo-Yankov
Copy link

Problem

Currently the timeout in NodeChannel._createUnaryClient is hardcoded to 10_000 ms. This period may not be enough in all cases - for example when using Hedera Local different machines or OSs may run the consensus nodes at different speeds and some are considerably slower than others. This can cause an unintended limitation on which contract methods can be executed through the SDK.

Solution

Add an option to configure the timeout period.

Alternatives

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants