Skip to content
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

Panicked at 'called Result::unwrap() on an Err value: InvalidPort' #2204

Closed
wirednkod opened this issue Apr 4, 2022 · 2 comments · Fixed by #2207
Closed

Panicked at 'called Result::unwrap() on an Err value: InvalidPort' #2204

wirednkod opened this issue Apr 4, 2022 · 2 comments · Fixed by #2207

Comments

@wirednkod
Copy link
Contributor

When trying to connect to a custom relay chain and parachain with substrate-connect (smoldot 0.6.10) the following error is received:

bindings-smoldot-light.jss:33 Uncaught (in promise) Error: panicked at 'called `Result::unwrap()` on an `Err` value: InvalidPort', /__w/smoldot/smoldot/bin/light-base/src/lib.rs:453:70
    at panic (bindings-smoldot-light.jss:33:1)
    at 00ec1f46:0x2b667
    at 00ec1f46:0x4344
    at 00ec1f46:0x248937
    at 00ec1f46:0x248019
    at 00ec1f46:0x24860c
    at 00ec1f46:0x253dde
    at 00ec1f46:0x254e91
    at 00ec1f46:0x1579b
    at 00ec1f46:0x137ee

Attached can be found the extension logs
and the specs used for relay (rococo-local-0.9.16 - relay specs.txt) and parachain
(Staging-latest-parachain-1.7.4 - parachain specs.txt…)

@tomaka
Copy link
Contributor

tomaka commented Apr 4, 2022

We clearly shouldn't panic, but it's because you wrote /tcp/ws/30335 instead of /tcp/30335/ws in one of the bootnodes

@wirednkod
Copy link
Contributor Author

wirednkod commented Apr 4, 2022

Thank you @tomaka . The specs were provided by Interlay's devops. Didn't realise that...

Edit: Changing it avoided the error. Should I let the issue open just for covering the panic in this edge case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants