You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Things I found so far that need to be updated to support dbt-core 1.5.0: (I was hoping that #32 would be enough, but it wasn't 😳)
the log output of dbt --log-format json ls --output json has changed compared to dbt-core 1.4.x which causes parsing of the result to fail. That should be pretty easy to fix.
Are there any other log output changes that need taken care of?
17:59:30 Traceback (most recent call last):
File "/Users/.../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/cli/requires.py", line 86, in wrapper
result, success = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Users/../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/cli/requires.py", line 71, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Users/../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/cli/requires.py", line 142, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Users/../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/cli/requires.py", line 168, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Users/../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/cli/requires.py", line 203, in wrapper
config.credentials.hashed_unique_field()
File "/Users/.../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/contracts/connection.py", line 144, in hashed_unique_field
return md5(self.unique_field)
^^^^^^^^^^^^^^^^^
File "/Users/.../code/dbt-invoke/venv_test/lib/python3.11/site-packages/dbt/adapters/sqlite/connections.py", line 40, in unique_field
return self.host
^^^^^^^^^
AttributeError: 'SQLiteCredentials' object has no attribute 'host'
The text was updated successfully, but these errors were encountered:
There doesn't appear to have been movement yet on dbt-sqlite supporting dbt-core 1.5. An alternative option could be to switch to dbt-duckdb.
Another change in dbt-core 1.5.0 that led to problems with dbt-invoke is described by dbt-labs/dbt-core#7465. It appears this will be fixed in dbt-core 1.5.2.
Things I found so far that need to be updated to support
dbt-core
1.5.0: (I was hoping that #32 would be enough, but it wasn't 😳)dbt --log-format json ls --output json
has changed compared todbt-core
1.4.x which causes parsing of the result to fail. That should be pretty easy to fix.dbt-sqlite
needs to supportdbt-core
1.5.0. Currently it will not run on 1.5.0 which will causedbt-invoke
tests to fail. An issue has been opened on thedbt-sqllite
repo (upgrade to support dbt-core v1.5.0 codeforkjeff/dbt-sqlite#43)The text was updated successfully, but these errors were encountered: