fix: grpc port check #14
Merged
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.
This pull request refactors the
IsGrpcPortfunction inpkg/utils/grpc.goto improve functionality and introduces a newGetNodeStatusfunction for more detailed gRPC port checks. It also updates imports to include new dependencies.Refactoring and new functionality:
pkg/utils/grpc.go: Replaced the originalIsGrpcPortimplementation with a call to the newly addedGetNodeStatusfunction, which checks the gRPC port by querying the node's status. TheIsGrpcPortfunction now logs debug information when the port is ready.pkg/utils/grpc.go: Added theGetNodeStatusfunction, which establishes a gRPC connection, queries the node's status usingnodev1beta1.ServiceClient, and returns the response. This provides more granular information about the gRPC port's readiness.Dependency updates:
pkg/utils/grpc.go: Importedlog/slogfor logging andcosmossdk.io/api/cosmos/base/node/v1beta1for node status functionality. Removed unusedgrpc/connectivityimport.