-
Notifications
You must be signed in to change notification settings - Fork 0
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
Confusing error message when ENTROPY_TUI_ENDPOINT
not set correctly, and failure to connect when setting the chain endpoint to localhost
#268
Comments
Ah, for annoying reasons documented elsewhere for the tui the env is currently ENTROPY_TUI_ENDPOINT worth nothing that error message is ueless tho |
@ameba23 please try the sdk docker scripts, see the instructions on the rc PR (on the sdk) |
I can confim things work fine the SDK docker scripts: I first jumpstart using the test cli to avoid confusion with different endpoint on the TUI and CLI:
Now lets check that alice is registered. Im not sure how to list registered accounts so use the test-cli:
Great. Now sign a message:
Excellent. So now i think the problem might be related to that i needed to Does |
ENTROPY_TUI_ENDPOINT
not set correctly, and difficulties using CLI with entropy-core docker-compose script
This is awesome, thanks for the clear write-up @ameba23 ❤️ |
$cat ~/.config/entropy-cryptography/entropy-cli.json | jq .endpoints.dev
"ws://127.0.0.1:9944" Sooo... "localhost" might be a problem. We should try |
entropy account ls | jq
[
{
"name": "mix",
"address": "5CBCdVRZDw8zTvnVkcrwSriAuJKLTnajLpZkz2BU4aNWgGNs",
"verifyingKeys": [] # <<< would have keys in here if registered
}
] |
Yep good catch that was it. With both the entropy-core and sdk docker compose environments, if i set the endpoint to the loopback interface So i can confirm i am able to register and sign messages on both setups. I'm very happy that we have the same behavior on both test setups cos otherwise this would be a fundamental flaw in how we are testing. |
ENTROPY_TUI_ENDPOINT
not set correctly, and difficulties using CLI with entropy-core docker-compose script ENTROPY_TUI_ENDPOINT
not set correctly, and failure to connect when setting the chain endpoint to localhost
Synthesis
|
What a rich bounty of Issues you've surfaced! ❤️ 🙏 I think I've split each problem you found out into their own issues. |
This is maybe an issue for the SDK rather that the CLI, but putting it here since steps to recreate involve the CLI, and i came across it when trying out the new release of the CLI.
It feels like i am using the wrong version of this CLI - but since there is no
--version
option and the ascii logo still displays core v0.1.0, cant be totally sure.I have npm version 9.5.0 and node version 18.15.0
I did:
So it looks like i have the right version installed
I am running a local test network with the docker compose script from entropy-core - NOT the docker script from the SDK. So i dont know if that makes a difference but ideally it shouldn't.
I am running the 0.3.0 release candidate - lets check that:
I have also checked i am able to register using the entropy-test-cli and the
//Alice
account.Lets try to register using the TUI:
Then with the TUI i create an account and attempt to register it. The account isn't funded so i don't expect this to work, but i hope for a nice error message:
This is strange, it seems like is is expecting version v0.2.0 which had 3 arguments to the register extrinsic (before key visibility was removed).
But i can see that in v0.3.0 of the SDK, only 2 arguments are used: https://github.com/entropyxyz/sdk/blob/faa9ddca18618e8d7d59134ee6c9e9fef40047a9/src/registration/index.ts#L90
Which makes me wonder if i am actually running the right version of the entropy CLI.
Lets try registering with the command line:
This is also strange, now it seems it cannot connect to the chain endpoint.
Lets double check that the chain endpoint is accessible with the other CLI:
I have the feeling that either i am somehow running the wrong version, or there are issues specific to the entropy-core docker compose setup as opposed to the SDK docker compose script which i assume is what yous are testing against.
Now lets try with zach's testnet, which is the only staging network on v0.3.0-rc.1 i currently know of:
not sure what went on there, but i'll try with the TUI:
hmm same as before.
Finally i try with the CLI again:
Yes! This is the desired behavior since that account isn't funded.
So it seems this is an issue related to the entropy-core docker-compose setup. However there is still the issue that there is different behavior with the TUI vs CLI.
I haven't managed to fund an account on Zach's staging network as for some reason the root account seems to be different than the one i have saved.
The text was updated successfully, but these errors were encountered: