My team has run into an issue since upgrading to

flytekit

1.10.2 (from 1.7.0) and I'm curious if others have run into something similar. If we have a python file that contains the definitions for the workflow, tasks, and launch plans, it fails to run in fast mode. It runs in non-fast mode fine. The error looks like this:

$ python3 workflow.py --inference_date=2024-01-07 --n_days_horizon=180

╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Traceback (most recent call last) ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ /.../workflow.py:319 in <module>                                                                                                                                                                                                                              │
│                                                                                                                                                                                                                                                                                                                                                                          │
│ ❱ 319 launch_plan = LaunchPlan.get_or_create(                                                                                                                                                                                                                                                                                                                            │
│                                                                                                                                                                                                                                                                                                                                                                          │
│ /.../lib/python3.10/site-packages/flytekit/core/launch_plan.py:273 in get_or_create                                                                                                                                                                                                                                              │
│                                                                                                                                                                                                                                                                                                                                                                          │
│ ❱ 273 │   │   │   │   raise AssertionError("The cached values aren't the same as the current c                                                                                                                                                                                                                                                                           │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
AssertionError: The cached values aren't the same as the current call arguments

If we move the launch plans to a separate file, we can run in fast mode. I created a github issue here: https://github.com/flyteorg/flyte/issues/4716

cc @Yee can you help with this. this seems like the bug in the caching logic - https://github.com/flyteorg/flytekit/blob/949bc1b40e1966b409c821b96011d900241b22fd/flytekit/core/launch_plan.py#L262

this is in local execution right?

Sorry to miss this @Yee! Someone posted a minimal example in the issue thread. https://github.com/flyteorg/flyte/issues/4716#issuecomment-1893423240

thanks.