JSON schema validation become broken after update from 1.60.2
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.61.1or higher
- OS Version: Windows 10
- Error “Unable to load schema from ‘https://bitbucket.${SOME_DOMAIN}/projects/${PROJECT_NAME}/repos/onboarding-document-schemas/raw/named-values.schema.json’: unable to get issuer certificate.(768)”
- Chrome and Edge works fine;
- For VPN connection I am using GlobalProtect;
- I’ve tried to use addon “win-ca”;
- I’ve tried to use other JSON addons with disabling the default one.
Steps to Reproduce:
- Install version 1.60.2
- Import CA certificates
- On that step it works.
- Update VSCode to new version.
- Stop working.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:6 (3 by maintainers)
Top Results From Across the Web
JSON schema validation broken after 5.9.0 - Katalon Community
We're noticing that the ability to do JSON schema validation using using everit's JSON validator referenced here appears to have broken ...
Read more >Erroneous successful validation by JSON-schema
The schema is malformed. (I'm ignoring the fact that the schema states entity should be "pde" or "topaz" , but the instances have...
Read more >JSON Schema Serializer and Deserializer
Both the JSON Schema serializer and deserializer can be configured to fail if the payload is not valid for the given schema. This...
Read more >JSON Schema Validation - Dependencies you can depend on
Being able to define a schema based on other properties can be a great benefit in that it can move application logic into...
Read more >How to Validate Your JSON Using JSON Schema
Imagine the following scenario: you and your teammate are working on a new feature. Your part is to create a JSON with some...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@chrmarti I had the same issue as @louisgv with version 1.65.2 that runs Node version 14.16.0. I tried again with VS Code Insiders version 1.66.0 that runs Node version 16.13.0 and it worked just fine.
@louisgv Are you behind a network proxy? Did this work previously?
Could you try with VS Code Insiders (https://code.visualstudio.com/insiders/)? That comes with a newer Node version which might included renewed certificates.