https://prefect.io logo
#prefect-dbt
Title
# prefect-dbt
g

Giacomo Chiarella

05/26/2023, 9:38 AM
Hi everyone! Any idea about this issue? At least from Prefect 2.10.0, Prefect is not usable
a

alex

05/26/2023, 2:00 PM
Hey @Giacomo Chiarella! we were investigating this issue yesterday, and we found that you can work around this issue by using the
.run()
method on the
DbtCoreOperation
block instead of calling
.trigger()
,
.wait_for_completion()
, and
.fetch_results()
in succession. I’ll post that in the issue for others to see, but hopefully, that unblocks you while we continue to investigate a fix.
g

Giacomo Chiarella

05/26/2023, 2:02 PM
Hi @alex thank you for the answer. Actually, the first thing I’ve checked has been looking in the
.run()
method to see if it was different, but to me seems the same as
.trigger()
,
.wait_for_complention()
,
.fetch_results()
. Also the stream_output = True seems not working
a

alex

05/26/2023, 2:11 PM
Hmmm, interesting. Can you share a minimal reproducible example for the error that you’re seeing when using the
.run()
method?
g

Giacomo Chiarella

05/26/2023, 2:13 PM
unfortunately I had to restore the Prefect instance as it was not usable, but the error was the same as in the issue and was I was running was just the .run() method body but not using .run(), just a copy-paste
a

alex

05/26/2023, 2:14 PM
Could you let me know if you still see the error after restoring your Prefect instance?
g

Giacomo Chiarella

05/26/2023, 2:16 PM
I will see, because I will need to upgrade again Prefect, this time in another instance, don’t know if I have time right now
if I will have time I will let you know
gratitude thank you 1
8 Views