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

Error sending request for url (http://localhost:8000/graphql) #3779

Closed
ayys opened this issue Apr 18, 2023 · 1 comment · Fixed by #3837
Closed

Error sending request for url (http://localhost:8000/graphql) #3779

ayys opened this issue Apr 18, 2023 · 1 comment · Fixed by #3837
Assignees
Milestone

Comments

@ayys
Copy link
Member

ayys commented Apr 18, 2023

Describe the bug

When using the wasmer login command with the --registry option to specify a registry URL, wasmer appends https:// to the url. This error occurs even though the specified URL is valid and points to a running registry.

$ wasmer -vV; rustc -vV

wasmer 3.2.0-beta.1 (82974ac 2023-03-23)
binary: wasmer-cli
commit-hash: 82974aca26b7d0a0a6f19f62a39a1d2ad07bdfad
commit-date: 2023-03-23
host: aarch64-apple-darwin
compiler: singlepass,cranelift
rustc 1.69.0-nightly (585f3eef2 2023-02-11)
binary: rustc
commit-hash: 585f3eef26f04440bca726c29193af7b4fa90e54
commit-date: 2023-02-11
host: aarch64-apple-darwin
release: 1.69.0-nightly
LLVM version: 15.0.7

Steps to reproduce

  1. Install wasmer-cli 3.2.0-beta.1
  2. Run wasmer login --registry 'http://localhost:8000/graphql' wapm_MYTOKEN.
$ wasmer login --registry 'http://localhost:8000/graphql' wapm_MYTOKEN
Error when trying to ping registry "https://http/://localhost:8000/graphql": error sending request for url (https://http//localhost:8000/graphql): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
WARNING: Registry "https://http/://localhost:8000/graphql" will be used, but commands may not succeed.
error: error sending request for url (https://http//localhost:8000/graphql): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
│   1: error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
│   2: dns error: failed to lookup address information: nodename nor servname provided, or not known
╰─▶ 3: failed to lookup address information: nodename nor servname provided, or not known

Expected behavior

I should be able to log in to a registry running locally oh http://localhost:PORT

Actual behavior

The cli force-prepends https:// to the registry URL.

@ptitSeb ptitSeb added this to the v3.3 milestone Apr 25, 2023
@ptitSeb
Copy link
Contributor

ptitSeb commented Apr 25, 2023

Nice to have in 3.3, but can go in 4.0 if planning is to tight

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.

3 participants