You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)
Issue details
If an Automation API script runs two or more subsequent operations (such as stack.up()) using inline programs, failure of every operation should be isolated to that operation, as one would expect. That is, if the first operation fails, it should not automatically imply that the second operation should fail.
This issue is a follow up to a report of problems in Python SDK #8633 and @joeduffy investigation showing that similar problems are affecting the Node SDK. So this is to track checking/testing this across languages:
Hello!
Issue details
If an Automation API script runs two or more subsequent operations (such as
stack.up()
) using inline programs, failure of every operation should be isolated to that operation, as one would expect. That is, if the first operation fails, it should not automatically imply that the second operation should fail.This issue is a follow up to a report of problems in Python SDK #8633 and @joeduffy investigation showing that similar problems are affecting the Node SDK. So this is to track checking/testing this across languages:
Resource Monitor has terminated, shutting down
error for all stacks after a stack error.聽#8633Steps to reproduce
Reproduction steps for Python in #8633
The text was updated successfully, but these errors were encountered: