Skip to main content

Troubleshoot the Databricks extension for Visual Studio Code

This article provides information about common errors that occur when using the Databricks extension for Visual Studio Code, as well as troubleshooting information. See What is the Databricks extension for Visual Studio Code?.

View Databricks log output​

The Databricks extension provides detailed log output in the Visual Studio Code View > Output panel when executing any type of command. You can use these logs to confirm success and to see any issues that might have occurred. Depending on the command, these logs are found in the following output channels:

  • Databricks Bundle Logs
  • Databricks Connect
  • Databricks Logs
  • Databricks Notebook

To switch output channels, select the dropdown in the top right corner of the Visual Studio Code Output view.

The Output view 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

Error when synchronizing through a proxy​

Issue: When you try to run the Databricks extension for Visual Studio Code to synchronize your local 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:

Bash
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.

Recommended 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 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.
  2. Attempt to reproduce your issue.
  3. From the Command Palette (View > Command Palette from the main menu), run the Databricks: Open full logs command.
  4. Send the databricks-cli-logs.json and sdk-and-extension-logs.json files that appear to Databricks Support.
  5. 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.
Last updated on