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] Condition "failure" branch results in "no branch satisfied" error #4483

Closed
2 tasks done
guyarad opened this issue Nov 27, 2023 · 1 comment · Fixed by #4528
Closed
2 tasks done

[BUG] Condition "failure" branch results in "no branch satisfied" error #4483

guyarad opened this issue Nov 27, 2023 · 1 comment · Fixed by #4528
Labels
backlogged For internal use. Reserved for contributor team workflow. bug Something isn't working exo

Comments

@guyarad
Copy link
Contributor

guyarad commented Nov 27, 2023

Describe the bug

Following the tutorial here. The "fail" else seems trivial enough and does fail the workflow. However, the message isn't visible anywhere in the UI or the execution when fetched via FlyteRemote object.

From the UI:
image

Expected behavior

The error should be "The input must be between 0 and 10".

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@guyarad guyarad added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Nov 27, 2023
Copy link

welcome bot commented Nov 27, 2023

Thank you for opening your first issue here! 🛠

@eapolinario eapolinario added backlogged For internal use. Reserved for contributor team workflow. exo and removed untriaged This issues has not yet been looked at by the Maintainers labels Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlogged For internal use. Reserved for contributor team workflow. bug Something isn't working exo
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants