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

staged-item-marked-completed #221

Closed
wants to merge 1 commit into from
Closed

Conversation

eg-lom
Copy link

@eg-lom eg-lom commented Nov 18, 2020

New status for failed task item with incomplete tasks should be running

New status for failed task item with incomplete tasks should be running
Copy link
Collaborator

@m4dcoder m4dcoder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's not enough context in this PR to understand what you are trying to achieve. Please provide detail example with workflow definition, expected behavior, and actual behavior in the description here. Also, there are many unit tests that are not passing which means this conflicts with other use cases.

@eg-lom
Copy link
Author

eg-lom commented Dec 7, 2020

I have raised an issue against it #222 with detail and example workflow. Will check the test cases.

@m4dcoder
Copy link
Collaborator

m4dcoder commented Dec 8, 2020

@eg-lom This issue is related to StackStorm/st2#5054 and there's an open discussion there on how to handle the situation and not break existing use/test cases. The current design of the workflow engine, by intention, is to fail fast. This means that if there is any failure in action execution (either for a task, or item for a task), the workflow engine will halt the workflow execution and terminate. Making changes to the status from FAILED to RUNNING is going to break a lot of test cases here plus the downstream test cases in https://github.com/StackStorm/st2. Please describe your use case in the linked issue here and make sure the community agrees with the design before hacking the changes here. Otherwise, we run the risk of many iteration of back and forth review and rework. Thanks.

@m4dcoder m4dcoder closed this Dec 8, 2020
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

Successfully merging this pull request may close these issues.

None yet

2 participants