[BUG] VSCode shows a Problem for a table not existing even though fusion builds successfully on snowflake

[mrhorvath]

Describe the bug
I receive the below problem in vscode (names changed) for any table which I use the source() function on in snowflake. This also prevents using column lineage, as I see 'No results returned' as a response from textDocument/codeLens in the dbt LSP trace. This is a new problem that did no exist in previous versions of LSP, but I don't know the last working version.

Importantly, the project still compiles, builds, and runs without any errors. The tables are built in the expected snowflake schema. I can view the table level lineage in the dbt plugin as well as preview the table. It is only in vscode problem list / column lineage where I see any problems.

[Trace - 4:07:23 PM] Received notification 'dbt/lspCompileComplete'.
Params: {
    "adapter_type": "snowflake",
    "adapter_unique_id": "a7cea0d56c5288275b0f5d226849fec3",
    "cause": "compileLspCommand",
    "compile_type": "full",
    "dbt_version": "2.0.0-preview.143",
    "duration_ms": 443,
    "errors": [
        {
            "code": "0214",
            "message": "dbt0214: Table 'SOME_TABLE' does not exist in schema SOME_DATABASE.SOME_SCHEMA\n  --> models/staging/source/stg_source__table_name.sql:4:5",
            "severity": "Error"
        }
    ],
    "models_count": 14,
    "project_id": "06e5b98c2db46f8a72cc4f66410e9b3b"
}

What version of dbt Fusion is this bug in? (find out by running dbt --version)
Extension Version: v0.50.0
Server Version: dbt-fusion 2.0.0-preview.143
dbt Version: dbt-fusion 2.0.0-preview.143

Is this a discrepancy between the dbt Fusion Engine and dbt Core? Check one.

• YES
• NO

To Reproduce

1. Create a table on snowflake for use as a source
2. Reference that table in a _sources.yml
3. Create a basic staging model using source() function
4. View the Problems list in vscode / attempt to use the column lineage feature on the staging model.

Expected behavior
DBT Fusion should download the schema and reference the tables with source() without errors.

Screenshots

Operating System and CPU Type (please complete the following information):

• Ubuntu Linux (WSL)
• X86

[Jeroendevr]

I can verify this also is the case for Fusion using Google BigQuery

[Trace - 14:23:24] Received notification 'dbt/lspCompileComplete'.
Params: {
    "adapter_type": "bigquery",
    "adapter_unique_id": "b2586c0a32194d6ee212dc9b1637e821",
    "cause": "compileLspCommand",
    "compile_type": "full",
    "dbt_version": "2.0.0-preview.143",
    "duration_ms": 3411,
    "errors": [
        {
            "code": "0214",
            "message": "dbt0214: Table '{}forecast' does not exist in schema {}.source_data_project_xml\n  --> {}hour_forecast.sql:5:19",
            "severity": "Error"
        },

Update

I do not know why exactly but it seems with dbt-fusion 2.0.0-preview.144 this issue is gone, it is also a day later so perhaps some cache could also have played a role.

[RPeachman]

Hey I have this issue on Snowflake for this version dbt-fusion 2.0.0-preview.144

[TIHan]

Will take a look.