-
Notifications
You must be signed in to change notification settings - Fork 986
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
BuggyShow-transfers
Query, doesn't yield anything, cli hangs and sometimes freezes the node
#2717
Comments
Adding to the debug studies, for some wallets ("new-wallet" wallet), instead of going into an infinite while for others ("test" wallet), it still goes into an "infinte" converting loop. Tested on two different nodes and giving different results |
When checking the balance (new-wallet), the screen shows balance and for some reason, CLI is trying to query the balance over a number of IBC channels? Could this be why its going into anor just Application Panic crashing? I only see this screen for the case where "Application panic crashed error" appeared For the test wallet where it went into a infinite loop of for "Changing current asset type >>>" the balance shows up without these error messages (test wallet) |
Apologies for tagging again, @brentstone Any thoughts on this when you get a chance to look into this? Thanks 🙂 |
This is related to #2381 since internally |
Great. Thanks for confirming the bug. |
Thanks for your report! We're actually going to remove this command, and replace it later with a faster option using an indexer. |
The
show-transfer
query parameter, which is very useful tool to get the list of confirmed transfers from a wallet, is not yielding anything but simply freezes the node when executed.The commands I have tried
For this testing, I created a new wallet and just had 1 transaction using it.However, even with that the query freezes and doesn't yield anything. Bringing it forward so it can be fixed as this is a very useful query tool to have.! @brentstone Tagging you here. Thanks
The text was updated successfully, but these errors were encountered: