https://linen.dev logo
Join Slack
Powered by
is anyone else running into an issue with dbt runn...
# plugins-dbt
j
is anyone else running into an issue with dbt running? I can't even get it to run, was working fine this morning (approx 10 hours ago), but now it is failing. Partial error message below:
Copy code
Extension executing `dbt deps`...
invoke failed with uncaught exception, please report to maintainer
Traceback (most recent call last):
  File "/home/runner/work/nba-monte-carlo/nba-monte-carlo/.meltano/utilities/dbt-duckdb/venv/lib/python3.10/site-packages/meltano/edk/extension.py", line 128, in pass_through_invoker
    self.invoke(None, command_args)
My dbt-ext config in my meltano.yml is in the thread.
Copy code
- name: dbt-duckdb
      namespace: dbt_ext
      label: dbt duckdb extension
      pip_url: dbt-core~=1.3.1 dbt-duckdb~=1.3.3 git+<https://github.com/meltano/dbt-ext.git>
      executable: dbt_invoker
      settings:
        - name: project_dir
          value: $MELTANO_PROJECT_ROOT/transform
          label: Projects Directory
        - name: skip_pre_invoke
          env: DBT_EXT_SKIP_PRE_INVOKE
          kind: boolean
          value: true
          description:
            Whether to skip pre-invoke hooks which automatically run dbt clean
            and deps
        - name: type
          env: DBT_EXT_TYPE
          value: duckdb
        - name: profiles_dir
          env: DBT_PROFILES_DIR
          value: $MELTANO_PROJECT_ROOT/transform/profiles/duckdb
          label: Profiles Directory
        - name: project_dir
          value: $MELTANO_PROJECT_ROOT/transform
          label: Projects Directory
        - name: path
          kind: string
          label: Path
          description:
            The path on your local filesystem where you would like the DuckDB
            database file and it's associated write-ahead log to be written.
        - name: schema
          kind: string
          value: main
          label: Schema
          description: Specify the schema to write into.
      commands:
        build:
          args: build
          description: Will run your models, tests, snapshots and seeds in DAG order.
        describe:
          args: describe
          executable: dbt_extension
        initialize:
          args: initialize
          executable: dbt_extension
      config:
        path: $MELTANO_PROJECT_ROOT/data/data_catalog/mdsbox.db
this has been working for the past 2 weeks, and no changes were made to my project today.
I wonder if this has anything to do with 
dbt-ext
p
I'm also getting errors as of today when running dbt deps but I get a different error 
TypeError: expected str, bytes or os.PathLike object, not tuple
j
Same error here, sorry, I snipped it too soon
e
@pat_nadolny does this only happen when running 
dbt deps
and no other command?
p
@edgar_ramirez_mondragon no for me it looks like its happening for all commands. Both meltano commands 
meltano invoke dbt-snowflake:deps
and pass through commands 
meltano invoke dbt-snowflake deps
this was after doing a fresh 
meltano install utility dbt-snowflake --clean
this morning
j
I have all my version pinned except for 
dbt-ext
which leads me to start there
Invoking dbt (any command) causes this error
e
Yeah, I’m looking into it. First issue seems to be that the 
*-ext
packages don’t have a tag or PyPI release of the EDK that they can reference so they’re all pointing to 
main
.
j
It worked at this timestamp: 
2023-01-16T19:20:47.199017Z
it DID not work (failed with the error above) at this timestamp: 
2023-01-17T06:01:02.478764Z
e
Yeah, I’m thinking https://github.com/meltano/edk/commit/19f57b7bbfe5476325abc5b7f55c64972b3c8b5c#diff-ddc0f7386a79ef5788c2a2a46b69a3d2f9e36db869aa9fa6045eab9b46de6574 was the offending change. But it fixed an incorrect use of the splat 
*
🤔. So either the initial type annotation was wrong, or all the 
-ext
packages have been using the API incorrectly.
j
happy to do some testing since its all wired into main currently 😄
t
@edgar_ramirez_mondragon do we have an issue open around this? i’d consider this a higher urgency bug and want to treat it as such.
e
@taylor we don’t. I’ll create one in the EDK repo now.
j
Fixed for me for now.
10 Views
Open in Slack
PreviousNext
Powered by