Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

<https://github.com/flyteorg/flytekit/pull/1721|#1721 Throw warning for nested @Task functions>
Pull request opened by <https://github.com/oliverhu|oliverhu>
[BUG] Nested <https://github.com/task|@task> invocations should not supported #3734

*TL;DR*

Address <https://github.com/flyteorg/flyte/issues/3734|flyteorg/flyte#3734> that nested Tasks/Workflows is not warned. In this PR, we fixed two things:

1. During local execution, pass proper `execution_state.mode` to `flyte_entity_call_handler`, so the underlying entity handler can create the correct FlyteContext (not always LOCAL_WORKFLOW_EXECUTION).
2. If `flyte_entity_call_handler` is invoked inside LOCAL_TASK_EXECUTION or TASK_EXECUTION, warn the users of nested tasks/workflows.

*Type*

☑︎ Bug Fix
☐ Feature
☐ Plugin

*Are all requirements met?*

☐ Code completed
☐ Smoke tested
☐ Unit tests added
☐ Code documentation added
☐ Any pending items have an associated Issue

*Complete description*

_How did you fix the bug, make the feature etc. Link to any design docs etc_

*Tracking Issue*

<https://github.com/flyteorg/flyte/issues/|https://github.com/flyteorg/flyte/issues/>

*Follow-up issue*

_NA_  
OR  
_<https://github.com/flyteorg/flyte/issues/|https://github.com/flyteorg/flyte/issues/>_
<https://github.com/flyteorg/flytekit|flyteorg/flytekit>
:white_check_mark: All checks have passed
2/2 successful checks

<https://github.com/flyteorg/flytekit/pull/1721|#1721 Throw warning for nested @Task functions>
Pull request ready for review by <https://github.com/oliverhu|oliverhu>
<https://github.com/flyteorg/flytekit|flyteorg/flytekit>

<https://github.com/flyteorg/flytekit/pull/1721|#1721 Throw warning for nested @Task functions>
Pull request closed by <https://github.com/oliverhu|oliverhu>
<https://github.com/flyteorg/flytekit|flyteorg/flytekit>