-
Notifications
You must be signed in to change notification settings - Fork 221
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
YAML(786) Unable to load schema #694
Comments
@kaysond Do you have any VPN/proxy on your laptop? |
@evidolob I do have a VPN, but it happens even when the VPN is disconnected. I am able to access the URL. |
Interestingly, I'm not seeing any http requests in the vscode dev tools (not sure if extension requests show up there or not...) |
I'm experiencing the same issue, but for a different schema;
I'm able to access the URL just fine using curl (and with web browsers). I'm not behind a proxy.
|
@evidolob is it possible to make the extension log the http return code when this fails? |
@kaysond Yes, it is possible |
I am experiencing this issue, too.
I can access the schema using curl:
I am using version 1.7.0 of the extension. Visual Studio Code Info: Version: 1.66.2 (Universal) |
I suddenly have the same error on all files, and like others I can access it manually just fine
|
same error
|
Hello @Vivapercuore , I am facing the same issue, can you please explain what do you mean by: access it manually on browser ? Thank you |
I don't know if this is related but I see the following warning in Logs (Extension Host)
No issue accessing https://json.schemastore.org/github-workflow.json from my browser. |
Hello @dkirrane I encounter the same issue when I am behind the company proxy, even though I have setup the http.proxy config etc |
Yip error disappears when I disable proxy on startup |
All schemas fail to load with the following environment:
The extension I use a VPN. Schemas can be downloaded with browser on Windows and wget on WSL. |
Same. It does seem an org proxy rollout maybe be the culprit, but I am not sure how with VS Code and the WSL Remote plugin ... |
open vpn and test in browser, make sure you can access the url, then reopen vscode |
This issue happens to me as well with the gitlab ci schema. Access works fine in the browser and on command line. VSCode fails without even trying to perform a network access. |
Ok, so I figured out the issue. The problem has to do with routing. In the specific case I had a route added that falsely routed traffic to the specific ip range that the server hosting the schema in question to a dummy interface ( a mixup of /8 vs /16 subnets ). That was very subtle to debug, and I still don't understand why the browser was able to resolve it fine while Vscode and some other IDEs could not. The fact that other IDEs also failed is what finally clued me in that something else must be wrong. So I would not discount that this is in fact purely a network issue in your case as well albeit it might be a subtle one. |
For those who face this issue and are behind corporate vpn and try to host JSON schemas internally: |
this worked for me however am not still sure where this is from |
How do I reload the IDE window? |
ctrl+shift+p => developer: reload window or just quit and restart |
I have encountered the same issue and share the same assumption as you. Our company utilizes Zscaler, and I have manually configured the ZScaler root and intermediate CA for Python requests, urllib libraries, as well as npm through environmental variables REQUESTS_CA_BUNDLE, SSL_CERT_FILE, and NODE_EXTRA_CA_CERTS. However, I am uncertain about the specific HTTP request library employed by the extension. To address this problem, it may be beneficial to include an option that allows users to specify the CA. This additional feature could potentially resolve the issue. |
I also encountered this issue for docker-compose files and I had a running VPN connection, but in split mode. I visited the URL which could not be resolved by the extension, did a reload of the environment, but it did not solve the problem. |
Encountered this issue because of my Web Application Firewall on my AWS Coudfront distribution. There is a rule configured by default: Added a custome route that allows requests to pass through for jsonschema files. |
Hi, is there a solution to this so far? Experience same error message, no Proxy, no VPN. Workaround with open it manually and refresh didn't work |
This really works, I'm curious on how it works |
work for me |
Same here, our company uses a different product but the result is that the tls certificate is rewritten. |
Describe the bug
I'm getting the following "Problem" on a yaml file.
Unable to load schema from 'https://www.graphql-code-generator.com/config.schema.json': Request vscode/content failed unexpectedly without providing any details.
This is loaded from the default catalog, and I'm able to access the schema via browser and using curl within the vscode terminal. Please let me know how I can help debug.
Expected Behavior
Schema is downloaded without problem
Current Behavior
Schema isn't loaded
Steps to Reproduce
Environment
The text was updated successfully, but these errors were encountered: