-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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: Better error msgs when node isn't synced #11449
Conversation
@@ -100,6 +100,19 @@ func GetAccountCmd() *cobra.Command { | |||
queryClient := types.NewQueryClient(clientCtx) | |||
res, err := queryClient.Account(cmd.Context(), &types.QueryAccountRequest{Address: key.String()}) | |||
if err != nil { | |||
node, err2 := clientCtx.GetNode() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to use err2
, you can safely shadow the existing err
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a case, where we have an err
from L101 and err
returned as nil
from L103 and L107 and catchingUp
is false
, then err would be nil which isn't true. I think having a separate variable makes sense here.
…khita/better-err-msgs-3412
Nice! Let's maybe add a changelog? |
Description
Closes: #3412
In this PR, we get node syncing info to check if it is catching up and added a better msg along with the error obtained
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change