-
Notifications
You must be signed in to change notification settings - Fork 202
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
[ux-bug] EthAccount error example during Wasm execute #2071
Comments
github-actions
bot
added
the
S-triage
Status: This issue is waiting on initial triage. More Info: https://tinyurl.com/25uty9w5
label
Oct 10, 2024
This was on commit 37913c4 |
Still happening on current main (f450c79) |
It turned out we were still running with an an old binary. This was fixed by spamming sudo rm "$(which nibid)" and then running just install Closing as this does not happen on main (f450c79), the initial audit version. |
github-project-automation
bot
moved this from ⚡ Building 🧱
to ✅ Completed
in ⚛️ Nibiru (Hougyoku)
Oct 10, 2024
Unique-Divine
removed
the
S-triage
Status: This issue is waiting on initial triage. More Info: https://tinyurl.com/25uty9w5
label
Oct 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Purpose / Abstract
Finally found a way to reproduce the error from NibiruChain/ts-sdk#371.
Update: False Alarm.
See #2071 (comment)
Error Case 1
Error Case 2
The text was updated successfully, but these errors were encountered: