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] List single task executions for a task doesn't work #542

Closed
1 of 20 tasks
katrogan opened this issue Oct 8, 2020 · 1 comment
Closed
1 of 20 tasks

[BUG] List single task executions for a task doesn't work #542

katrogan opened this issue Oct 8, 2020 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@katrogan
Copy link
Contributor

katrogan commented Oct 8, 2020

Describe the bug
Because generated workflow definitions for a single task execution are marked as SYSTEM_GENERATED admin filters out these workflows on list calls. Similarly, the generated launch plans are marked inactive and also filtered.

Expected behavior
It should be possible to list single task executions for a task.

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlytePropeller
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlyteAdmin (Control Plane service)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other

To Reproduce
Steps to reproduce the behavior:

  1. ...
  2. ...

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
Flyte component ALL

  • Sandbox (local or on one machine)
  • Cloud hosted
    • AWS
    • GCP
    • Azure
  • Baremetal
  • Other

Additional context
Add any other context about the problem here.

@katrogan katrogan added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Oct 8, 2020
@katrogan katrogan self-assigned this Oct 8, 2020
@katrogan
Copy link
Contributor Author

katrogan commented Oct 8, 2020

cc @schottra

@katrogan katrogan removed the untriaged This issues has not yet been looked at by the Maintainers label Oct 8, 2020
@kumare3 kumare3 added this to the 0.9.0 milestone Oct 15, 2020
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
* fix: upgrade react-flow-renderer version

Signed-off-by: James <james@union.ai>

* fix: use setTimeout for queue on the next render

Signed-off-by: James <james@union.ai>

* fix: use one state variable and fitView after nodesChange

Signed-off-by: James <james@union.ai>

* fix: graph edge overlaps nodes issue

Signed-off-by: James <james@union.ai>

* introduce needFitView

* edge overlap
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Jul 24, 2023
…ion for ray (flyteorg#542)

Signed-off-by: Daniel Rammer <daniel@union.ai>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Jul 24, 2023
Signed-off-by: Yee Hing Tong <wild-endeavor@users.noreply.github.com>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 9, 2023
…ion for ray (flyteorg#542)

Signed-off-by: Daniel Rammer <daniel@union.ai>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
Signed-off-by: Yee Hing Tong <wild-endeavor@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants