Jon10/10/2022, 2:38 PM
. Why is the flow trying to run when I register it?
AttributeError: 'Parameter' object ...
Angel Acosta10/10/2022, 3:24 PM
Andrew Reeve10/12/2022, 8:48 AM
Oluremi Akinwale10/12/2022, 4:01 PM
Zi Yuan10/17/2022, 7:28 AM
Bebeto Nyamwamu10/18/2022, 4:12 AM
Daniel Mak10/19/2022, 8:20 AM
into my flow as I would need to use that as a parameter for my pipeline? E.g runs on Wed 19Oct 2022 23:00. the date parameter
is passed a parameter into the flow and will be used in the ETL script
Sam Werbalowsky10/19/2022, 8:48 PM
as part of a CI was awesome) so that we don’t have to worry about competing dev environments. ◦ I think maybe what we’d want to do now for this is to use S3 storage, since it looks like git storage is only for public repos right now. • Different docker images for diferent flows: ◦ It looks like in V2, Agents are what the executors (?) in V1 were. Would using different images for different flows mean that we needed to have different agents available?
Brett Naul10/24/2022, 4:01 PM
? the docs are pretty barebones compared to say the Azure equivalent. for me
is just hanging infinitely with no output but it's hard to say where I went wrong without an example to go off of.
Richard Alexander10/25/2022, 2:43 PM
Jon10/26/2022, 1:03 PM
Tim-Oliver10/28/2022, 9:16 AM
Rabea Yousof10/30/2022, 10:41 AM
terrence11/01/2022, 3:09 PM
eddy davies11/01/2022, 4:59 PM
Ethan Homan11/02/2022, 7:09 PM
It would be great to provision a small Fargate task with a Docker image with just the DBT project for the first one, and then provision an ECS task with significantly larger resources and a different Docker image for the ML training job. Is there a way to do this by creating dependencies between Prefect deployments or by specifying infrastructure at the task or sub-flow level?
(DBT job on Snowflake) -> (ML training job).
Michiel Verburg11/03/2022, 9:09 AM
Brad Clark11/04/2022, 4:14 PM
as described here https://prefecthq.github.io/prefect-gcp/. I'm tryin to provide some direction to our data engineers
Stephen Thibeault11/07/2022, 2:55 PM
Khuyen Tran11/10/2022, 5:01 PM
to subflows so that they can wait for upstream tasks. In the example below,
didn’t run because the
task failed. This feature is available in Prefect 2.6.6.
Khuyen Tran11/11/2022, 5:31 PM
Khuyen Tran11/11/2022, 11:05 PM
Tim-Oliver11/14/2022, 1:57 PM
Khuyen Tran11/15/2022, 4:59 PM
View more here. Kudos to @Andrew Huang for this cool feature.
import asyncio from prefect import flow, get_run_logger @flow async def test_async_flow(): await asyncio.sleep(3) logger = get_run_logger() logger.debug("a debug") <http://logger.info|logger.info>("my info") logger.warning("some warning") logger.critical("super critical") logger.error("error!") print('all done') @flow def test_sync_flow(): test_async_flow() test_sync_flow()
Khuyen Tran11/17/2022, 4:11 PM
and the task takes longer than
seconds to execute, Prefect will raise a TimeOut error. View more here. Kudos to @Peyton Runyan for this feature.
Jon11/23/2022, 1:48 AM
Edmondo Porcu11/29/2022, 12:39 AM
Khuyen Tran11/30/2022, 4:32 PM
View more styles in Rich’s documentation.
from prefect import flow, get_run_logger @flow def cow_say(): logger = get_run_logger() <http://logger.info|logger.info>("I'm in [red]danger[/red]!") if __name__ == "__main__": cow_say()
John Kang12/01/2022, 8:40 PM
Jon12/09/2022, 7:37 PM