[Bug] Encountered an error while generating catalog: 'NoneType' object has no attribute 'lower' about dbt-core HOT 3 CLOSED

Thanks for raising this issue @hantmac !

Can you share more details how you are getting this error? i.e., if you are using a programmatic invocations Python script, could you share it along with a minimal set of dbt project files that reproduces this issue?

Looking at the logs, it looks like you are using a beta version of the dbt-databend adapter. For some reason, it looks like it is executing the TestDocsGenerateSnowflake test (inherited from here).

from dbt-core.

Thanks for raising this issue @hantmac !

Can you share more details how you are getting this error? i.e., if you are using a programmatic invocations Python script, could you share it along with a minimal set of dbt project files that reproduces this issue?

Looking at the logs, it looks like you are using a beta version of the dbt-databend adapter. For some reason, it looks like it is executing the TestDocsGenerateSnowflake test (inherited from here).

Thanks for response! I just write a test case for dbt-databend, the python code is as follows:

class TestDocsGenerateDatabend(BaseDocsGenerate):
    pass

from dbt-core.

This is the Python error that crops up any time you call lower() on a non-string object.

So one possibility is that your adapter is passing a None Relation around, and it's ending up here (or somewhere else).

BaseDocsGenerate is extended without issue by dbt-postgres, dbt-snowflake, etc. without issue.

So my belief is that this isn't an issue in dbt-core dbt-adapters, but rather that there's a bug somewhere in dbt-databend that is causing there to be a non-string Relation object, and this test is exposing it. So I'm going to close this issue as "not a bug".

from dbt-core.