AltimateAI / AltimateAI/vscode-dbt-power-user

Error when running project health check

Offen
#1,552 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
JavaScript
Sterne
585
Forks
121
Ø Merge
5 T. 39 Min.
Gemergte PRs (30 T.)
4

Beschreibung

### Expected behavior

When running a health check, it should run and produce output

### Actual behavior

When I run a project health check regularly against a dbt-databricks project, the operation ends without any output.

When I run it with debug log level, I get the following error.
```
2025-01-17 08:59:21.751 [debug] altimateScane:getProblems:Error occurred for project [{"exception":{"type":{"name":"Exception","module":"builtins"},"message":"DatabricksAdapter.get_catalog() missing 1 required positional argument: 'used_schemas'","args":["DatabricksAdapter.get_catalog() missing 1 required positional argument: 'used_schemas'"],"format":["Exception: DatabricksAdapter.get_catalog() missing 1 required positional argument: 'used_schemas'\n"]},"traceback":{"lineno":104,"strack
```

### Steps To Reproduce

Just running the project health check "Start Scan"

### Log output/Screenshots

```
2025-01-17 08:59:21.751 [debug] altimateScane:getProblems:Error occurred for project [{"exception":{"type":{"name":"Exception","module":"builtins"},"message":"DatabricksAdapter.get_catalog() missing 1 required positional argument: 'used_schemas'","args":["DatabricksAdapter.get_catalog() missing 1 required positional argument: 'used_schemas'"],"format":["Exception: DatabricksAdapter.get_catalog() missing 1 required positional argument: 'used_schemas'\n"]},"traceback":{"lineno":104,"strack
```

### Operating System

MacOS 15.2

### dbt version

1.9.1

### dbt Adapter

databricks 1.9.1

### dbt Power User version

0.51.2

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.