Hi everyone! Our prefect 2 to 3 migration has encountered a fun issue. When using ecs-workers to spin up flows as transient ecs tasks, some of those tasks are failing via
signal only works in main thread of the main interpreter
. Does anyone familiar with the internals know if the way prefect runs ecs tasks has changed in v3 such that our tasks might not be running in the main interpreter?
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.