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

feat: add Held status to exState status #457

Merged
merged 1 commit into from
Sep 13, 2023
Merged

Conversation

kanej
Copy link
Member

@kanej kanej commented Sep 11, 2023

To support execution strategies returning hold status in the future,
we are adding it into the execution status of exStates.

Resolves #451

TODO

  • Add the status
  • Update the return result
  • Do we need a strategy message now that can return an on hold result?
  • Do we need rerun rules? Or can they be deferred until we release execution strategies.

@kanej kanej force-pushed the feat/add-hold-status branch from 2e24167 to 2441256 Compare September 11, 2023 13:09
@kanej kanej force-pushed the feat/add-hold-status branch 2 times, most recently from 1b72bdc to ab02ffb Compare September 12, 2023 09:53
@kanej
Copy link
Member Author

kanej commented Sep 12, 2023

I am opting to leave the run logic until we are actually exposing strategies that can use held.

@kanej kanej marked this pull request as ready for review September 12, 2023 09:59
@kanej kanej requested a review from alcuadrado September 12, 2023 09:59
@kanej kanej changed the title feat: add Hold status to exState status feat: add Held status to exState status Sep 12, 2023
@@ -217,6 +217,12 @@ function convertExecutionResultToEventResult(
error: "Transaction reverted",
};
}
case ExecutionResultType.STRATEGY_HELD: {
Copy link
Member

Choose a reason for hiding this comment

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

Sorry for being repetitive, but held shouldn't be considered an error.

Copy link
Member Author

Choose a reason for hiding this comment

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

I have added another event result (held), to allow mapping from held to a non-error result. And wired it through the UI.

To support execution strategies returning `held` status in the future,
we are adding it into the execution status of exStates.

The return result of a deployment can now include a held property
listing the futures that have been held and the reason for the hold.

This is wired through to the ui as a new sort of Held result instead of
treating it as success or failure.

Resolves #451
@kanej kanej force-pushed the feat/add-hold-status branch from 54ed809 to 85d6973 Compare September 13, 2023 22:56
@kanej kanej merged commit ab6f8b0 into development Sep 13, 2023
6 checks passed
@kanej kanej deleted the feat/add-hold-status branch September 13, 2023 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Reintroduce Hold
2 participants