Jeremy Cohen
Jeremy Cohen
@curtis-trynow-io I'm going to transfer this to the `dbt-core` repo, since that's where our Dockerfile lives, along with the actions to build + release our Docker images for each version....
@curtis-trynow-io I'm going to close this one for now. Our official policy, for the time being, is that we can provide users with the Dockerfile to build their own images,...
@zsvoboda Thanks for opening! It sounds like this is cropping up [here in `dbt-spark`](https://github.com/dbt-labs/dbt-spark/blob/ed8a17036be15ce929a068e2daeaf7433573778a/dbt/adapters/spark/connections.py#L284), where we're running the equivalent of: ``` from dbt.events import AdapterLogger logger = AdapterLogger("Spark") ... except...
Detailed timing information (including timestamps) would be available from the structured logging interface, which is where we're investing more of our effort around dbt Core metadata going forward
Related: https://github.com/dbt-labs/dbt-snowflake/issues/82#issuecomment-1315392698 Even though the `response` object is available from failing queries, because of the way we `try` materialization macros and bubble up any exceptions, we don't plumb the `adapter_response`...
@jesperdejby Thanks for opening, and for the clear restatement! I was able to reproduce this quite easily. Indeed, the issue here is that, when `target.name` is _not_ `prod`, the Jinja...
@dbeatty10 I think you're right on the money! A `cast()` here should do the trick, and it's fair that a user would expect this to work. One thing I did...
Agree that this would be valuable! My sense is that the log message here is coming from the `RunningOperationCaughtError` event: https://github.com/dbt-labs/dbt-core/blob/72ecd1ce74641ea0675399f251564cc7f7fbf974/core/dbt/task/run_operation.py#L58-L61 https://github.com/dbt-labs/dbt-core/blob/72ecd1ce74641ea0675399f251564cc7f7fbf974/core/dbt/events/types.py#L1132-L1138 The line numbers here are from the database...
@albertovpd Thanks for opening! I tried this out locally, and I found that `test` is just completely ignored. Only tests defined under the `tests` key (correctly named) were actually defined...
@yashbhatianyt Thanks for opening, and sorry for the delay getting back to you! I can't speak to the specific implementation you're pursuing around Google Cloud functions / Google Cloud Run....