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

Distinguish "killed by orchestrator" and actual failures #84

Open
romain-intel opened this issue Oct 28, 2022 · 0 comments
Open

Distinguish "killed by orchestrator" and actual failures #84

romain-intel opened this issue Oct 28, 2022 · 0 comments

Comments

@romain-intel
Copy link
Contributor

Summary

When a task dies, it can kill all the other concurrently running task and the UI does not distinguish these two "deaths"

Motivation

With a wide foreach, if there is a single failure somewhere, it can be difficult to figure out which one it is because all the tasks are marked as failed. It may be nice to be able to distinguish "user failure" from "killed by orchestrator" type of failures so the user may more easily narrow down on the actual cause of the failure.

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

No branches or pull requests

1 participant