[frontend] artifacts [unknown] pipeline/workspace

[axel7083]

Environment

• How did you deploy Kubeflow Pipelines (KFP)? manifests
• KFP version: 2.0.0

Description

No matter how I start my run, (from UI or SDK) I always get the [unknown] in the Artifact panel for pipeline/workspace.

Expected result

The name of the pipeline.

---

Impacted by this bug? Give it a 👍.

[khituras]

I saw your PR for that. Did you find any workaround in the meantime?

[axel7083]

I saw your PR for that. Did you find any workaround in the meantime?

Sadly, no, looking for the pipeline name was kinda hard as explained in the PR, maybe a metadata was not added properly or a CustomProperties. But from the current element, I inspected the networks logs in the current version, and there is not the pipeline name attached.

Edit

I am not a big fan of my implementation in the PR, since it had a lot of requests, just like the pipeline run page where I opened an issue #9701 explaining that we get a very long time for displaying all the informations, I simply used the same logic in the artifacts page to get all the pipeline information.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[HumairAK]

/remove lifecycle/stale

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[google-oss-prow]

@AndersBennedsgaard: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[AndersBennedsgaard]

@HumairAK or @axel7083 would you mind re-opening this issue? I also see artifacts as [unknown] on KFP 2.2.0, so I don't think it has been fixed

[axel7083]

/reopen

[google-oss-prow]

@axel7083: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[rimolive]

/assign @rimolive

[thesuperzapper]

I can confirm that this issue affects Kubeflow Pipelines 2.1.0.

[rimolive]

I tested the code changes in #9772, but we should definitely think of a proposal that involves backend changes too. The code in that PR makes frontend response times go crazy, specially the grouped list, which took me ~19 minutes to render with the PR change.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[HumairAK]

AFAIK this is not resolved it

/reopen

[google-oss-prow]

@HumairAK: Reopened this issue.

In response to this:

AFAIK this is not resolved it

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[HumairAK]

/remove-lifecycle stale