Andrew S. Rosen

Note to self: this does not seem related to https://github.com/PrefectHQ/prefect/issues/14036 since the errors persist in 3.0.0rc15.

We know that the following always works: ```python from prefect import task, flow @task def my_task(): return 1 @flow def my_subflow(dummy): return 1 @flow def my_flow(): result = my_task.submit() return...

Prefect 3 support will be fixed with the upstream Prefect PR I opened: https://github.com/PrefectHQ/prefect/pull/14900.

Thanks! Let me first address one of your points/questions before proceeding: > I don't quite understand the logic in change_settings_wrap, so there's probably some overlap / considerations there if it...

This seems logical. I did some refactoring to reduce code duplication. Before this can be merged, the following will need to be addressed: - It does not currently work when...

Pinging @honghuikim since you may be interested in this PR based on your prior contribution.

Thank you, @honghuikim, for this very interesting suggestion! It would be great if we could have the logic inside something like `customize_funcs` that way we don't have to deal with...

> However, putting this in customize_funcs means that only flows that explicitly call that will actually update right? I wouldn't be surprised if some flows/recipes don't use that. Something that...

Following up the discussion here to state that packing this logic inside `customize_funcs` is not actually as good of an idea as it may initially seem. While most `@flow`s in...

@tomdemeyere: Thank you for your contribution here! This looks quite nice. I do not have any particular comments other than that I would be pleased to merge this. Regarding testing,...