Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] <Bug Name> #11572

Open
HumairAK opened this issue Jan 30, 2025 · 0 comments
Open

[bug] <Bug Name> #11572

HumairAK opened this issue Jan 30, 2025 · 0 comments

Comments

@HumairAK
Copy link
Collaborator

Environment

  • How do you deploy Kubeflow Pipelines (KFP)? standalone and multi-user

  • KFP version: 2.4

To find the version number, See version number shows on bottom of KFP UI left sidenav. -->

  • KFP SDK version: 2.11

Steps to reproduce

  • Use a simple dag pipeline like the following:
@dsl.component()
def fail():
    import sys
    sys.exit(1)

@dsl.component()
def hello_world():
    print("hellow_world")

@dsl.component()
def post_msg():
    print(f"this is a message")

@dsl.pipeline
def pipeline():
    post_msg_task = post_msg().set_caching_options(enable_caching=False)
    with dsl.ExitHandler(exit_task=post_msg_task):
        hello_task = hello_world().set_caching_options(enable_caching=False)
        fail_task = fail().set_caching_options(enable_caching=False)
        fail_task.after(hello_task)


compiler.Compiler().compile(
    pipeline_func=pipeline,
    package_path=__file__.replace('.py', '-v2.yaml'))

Or any other control flow that utilizes sub dags, i.e. loops, nested pipelines, exit handlers, etc.

Expected result

The subdag status should stay as loading until all tasks are completed.

Materials and reference

dag-status-behavior.webm

Labels

/area backend


Impacted by this bug? Give it a 👍.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant