opening notebook in Azure ML with VSCode (web) fails

Question

Attempting to open notebooks with VSCode (web) and getting a Fatal Error that states "Please check Developer Tools" on a black page.

Opening Developer Tools, I see the following error:

VM16 webOpener.js:2 Refused to create a TrustedTypePolicy named '@azure/ms-rest-js#xml.browser' because it violates the following Content Security Policy directive: "trusted-types amdLoader cellRendererEditorText defaultWorkerFactory diffEditorWidget diffEditorWidget2 diffReview domLineBreaksComputer dompurify editorGhostText editorViewLayer notebookRenderer stickyScrollViewLayer tokenizeToString".

This is happening for all of my users on any workspace, and from both Edge and Chrome.

Answer 1

@Chris Smith Please report this issue in the below VS code GitHub channel:

https://github.com/microsoft/vscode/issues

.

.

Sharing 2 more threads for the similar issue in VS Code:

https://github.com/microsoft/vscode/issues/221570

https://github.com/microsoft/vscode/issues/184755

Hope this helps.

Answer 2

Possible Solutions

1. Clear Browser Cache and Cookies

• Sometimes cached files can cause issues.
• Action: Clear your browser's cache and cookies, then restart the browser and try again.

2. Disable Extensions

• Some browser extensions can interfere with CSP.
• Action: Try disabling extensions, particularly those related to security or content filtering, and then reload the VSCode web page.

3. Use Incognito Mode

• Open a new incognito window in your browser.
• Action: This mode runs without extensions and with a fresh session, which can help identify if the issue is related to your browser settings or extensions.

4. Check for Updates

• Ensure that both your web browser and VSCode web are up to date.
• Action: Sometimes, compatibility issues arise from outdated software.

5. Content Security Policy Configuration

• If you're managing your own deployment or using a self-hosted instance, check the configuration for your Content Security Policy.
• Action: Ensure that the policy allows the creation of Trusted Types as needed.

6. Using Different Browsers

• While you've mentioned trying both Edge and Chrome, you might want to test with Firefox or another browser.
• Action: See if the issue is browser-specific.

7. Open Developer Tools Console

• In the Developer Tools console, check for any additional errors or warnings that might provide more context.
• Action: Look for network errors, additional CSP violations, or script loading issues.

8. Reinstall VSCode

• If the issue persists, consider reinstalling VSCode.
• Action: This might help resolve any corrupted settings or configurations. Possible Solutions
  1. Clear Browser Cache and Cookies
  • Sometimes cached files can cause issues.
  • Action: Clear your browser's cache and cookies, then restart the browser and try again.
  2. Disable Extensions
  • Some browser extensions can interfere with CSP.
  • Action: Try disabling extensions, particularly those related to security or content filtering, and then reload the VSCode web page.
  3. Use Incognito Mode
  • Open a new incognito window in your browser.
  • Action: This mode runs without extensions and with a fresh session, which can help identify if the issue is related to your browser settings or extensions.
  4. Check for Updates
  • Ensure that both your web browser and VSCode web are up to date.
  • Action: Sometimes, compatibility issues arise from outdated software.
  5. Content Security Policy Configuration
  • If you're managing your own deployment or using a self-hosted instance, check the configuration for your Content Security Policy.
  • Action: Ensure that the policy allows the creation of Trusted Types as needed.
  6. Using Different Browsers
  • While you've mentioned trying both Edge and Chrome, you might want to test with Firefox or another browser.
  • Action: See if the issue is browser-specific.
  7. Open Developer Tools Console
  • In the Developer Tools console, check for any additional errors or warnings that might provide more context.
  • Action: Look for network errors, additional CSP violations, or script loading issues.
  8. Reinstall VSCode
  • If the issue persists, consider reinstalling VSCode.
  • Action: This might help resolve any corrupted settings or configurations.