We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to Reproduce:
GET http://whatever.local/api/v1/blah
Expect to get ~equivalent behaviour to using curl on the command line. Instead, get getaddrinfo EAI_AGAIN whatever.local error
getaddrinfo EAI_AGAIN whatever.local
Example of curl on the same system:
$ curl -v http://whatever.local/api/v1/blah * Host whatever.local:80 was resolved. * IPv6: (none) * IPv4: 192.168.88.28 * Trying 192.168.88.28:80... * Connected to whatever.local (192.168.88.28) port 80 > GET /api/v1/blah HTTP/1.1 <<<snipped more>>>
Presumably vscode is doing it's own resolution?
The text was updated successfully, but these errors were encountered:
It appears this is a flatpak issue, though I've no idea how to fix it : <
$ flatpak run --share=network --devel --command=curl org.fedoraproject.Platform http://whatever.local/api/v1/blah curl: (6) Could not resolve host: whatever.local $ ping whatever.local PING fwupd-otademo.local (192.168.88.28) 56(84) bytes of data. 64 bytes from 192.168.88.28: icmp_seq=1 ttl=64 time=2.80 ms ... $ flatpak run --share=network --devel --command=curl org.fedoraproject.Platform http://192.168.88.28/api/v1/blah { // Some valid response }
Sorry, something went wrong.
No branches or pull requests
Steps to Reproduce:
Expect to get ~equivalent behaviour to using curl on the command line.
Instead, get
getaddrinfo EAI_AGAIN whatever.local
errorExample of curl on the same system:
Presumably vscode is doing it's own resolution?
The text was updated successfully, but these errors were encountered: