Ilia Babanov

Hey, can you share additional logs with us? You can find them in the "Databricks" output channel in the VSCode, or check log files directly by executing `Databricks: Open full...

Closing the issue as it's quite old and there was no new responses. Related to this: keep in mind that we've released v2 extension where sync destination is based on...

Closing this issue as stale, sorry for not replying in time. If you are still having similar issues, please checkout this https://github.com/databricks/databricks-vscode/issues/1540, there's context on how to run pytests in...

Hey, we currently don't have remote cell-by-cell execution on the roadmap. You can execute [notebooks cell by cell with dbconnect](https://docs.databricks.com/aws/en/dev-tools/vscode-ext/notebooks) (where spark code will be executed remotely, but everything else...

Closing this in favor of https://github.com/databricks/databricks-vscode/issues/472

Closing this in favor of https://github.com/databricks/databricks-vscode/issues/472

@a-tanman thanks for the pointer, that part of the code is indeed problematic, created a fix here: https://github.com/databricks/databricks-vscode/pull/1266

Published new release (1.3.1) with the fix. @cyaris can you update the extension, make sure databricks connect is enabled, and try running notebooks again?

@nilskk-t can you provide reproduction steps? In the v2 version of the extension we no longer inject databricks env vars into terminals, so you shouldn't see issues when running CLI...

Hi, this can happen it you've changed an auth in the extension, but haven't restarted your local notebook kernel. Can you try restarting and re-running? We also show this notification...