Troubleshoot the Databricks extension for Visual Studio Code

This article provides troubleshooters for the Databricks extension for Visual Studio Code. See What is the Databricks extension for Visual Studio Code?.

Error when synchronizing through a proxy

Issue: When you try to run the Databricks extension for Visual Studio Code to synchronize your local code project through a proxy, an error message similar to the following appears, and the synchronization operation is unsuccessful: Get "https://<workspace-instance>/api/2.0/preview/scim/v2/Me": EOF.

Possible cause: Visual Studio Code does not know how to find the proxy.

Recommended solution: Restart Visual Studio Code from your terminal by running the following command, and then try synchronizing again:

env HTTPS_PROXY=<proxy-url>:<port> code

In the preceding command:

  • Replace <proxy-url> with the full URL to your proxy.

  • Replace <port> with the correct port on your proxy.

Error: “spawn unknown system error -86” when you try to synchronize local code

Issue: When you try to synchronize local code in a project to a remote Databricks workspace, the Terminal shows that synchronization has started but displays only the error message spawn unknown system error -86. Also, the Sync Destination section of the Configuration pane remains in a pending state.

Possible cause: The wrong version of the Databricks extension for Visual Studio Code is installed for your development machine’s operating system.

Recommend solution: Uninstall the extension, and then Install and open the extension for your development machine’s operating system from the beginning.

Send usage logs to Databricks

If you have issues synchronizing local code to a remote Databricks workspace, you can send usage logs and related information to Databricks Support by doing the following:

  1. Turn on verbose mode for the Databricks command-line interface (CLI) by checking the Bricks: Verbose Mode setting, or setting databricks.bricks.verboseMode to true, as described in Settings for the Databricks extension for Visual Studio Code.

  2. Also turn on logging by checking the Logs: Enabled setting, or setting databricks.logs.enabled to true, as described in Settings for the Databricks extension for Visual Studio Code. Be sure to restart Visual Studio Code after you turn on logging.

  3. Attempt to reproduce your issue.

  4. From the Command Palette (View > Command Palette from the main menu), run the Databricks: Open full logs command.

  5. Send the bricks-logs.json and sdk-and-extension-logs.json files that appear to Databricks Support.

  6. Also copy the contents of the Terminal (View > Terminal) in the context of the issue, and send this content to Databricks Support.

To send error logs that are not about code synchronization issues to Databricks Support:

  1. From the Command Palette (View > Command Palette), run the Databricks: Open full logs command.

  2. Send only the sdk-and-extension-logs.json file that appears to Databricks Support.

The Output view (View > Output, Databricks Logs) shows truncated information if Logs: Enabled is checked or databricks.logs.enabled is set to true. To show more information, change the following settings, as described in Settings for the Databricks extension for Visual Studio Code:

  • Logs: Max Array Length or databricks.logs.maxArrayLength

  • Logs: Max Field Length or databricks.logs.maxFieldLength

  • Logs: Truncation Depth or databricks.logs.truncationDepth