Formatted dbt errors

[Auric-Manteo]

What's the use case?

If a dbt run fails I want to easily read the error.
The current error message is unformatted - it misses newlines as shown in the screenshot.

Ideas of implementation

Add the newlines to the error messages as you would see when running dbt in a command line.
+1 if we could get some highlighting on the actual error :D

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[garethbrickman]

It's strange and unexpected that you would be encountering a pop-up error like that. What actions are you taking before it appears?

Typically when materializing dbt assets there will be a run in Dagster and the formatted dbt logs are available in the run's stdout tab for both successful and failed runs.

[Auric-Manteo]

Hi,
I don't see any details in stdout. The place I am looking at is the Events tab where you can click to see the entire message of the failed dbt command which then shows the popup I posted above.

[garethbrickman]

Do you still not see any details if you select the step in the chart first?

[Auric-Manteo]

Yes, this tab is always blank. I think it's due to the way dagster is set up.
I tried to dig into it before, but didn't get it to work. I hazily remember something about compute logs :D

Anyway, I guess technically that is another issue.

[garethbrickman]

Yeah it's not typical for dbt CLI logs to be shown in the error as for you- typically our stack trace will refer to look in stderr precisely because they can be lengthy and can be formatted there.