Skip to content

[OCTRL-1064] GO_ERROR calls should never be critical#693

Merged
knopers8 merged 1 commit intomasterfrom
knopers8-patch-8
Oct 30, 2025
Merged

[OCTRL-1064] GO_ERROR calls should never be critical#693
knopers8 merged 1 commit intomasterfrom
knopers8-patch-8

Conversation

@knopers8
Copy link
Collaborator

Having to handle a failed GO_ERROR transition is something we should avoid. An interrupted GO_ERROR means that we might not perform the complete procedure and miss e.g. calling some services/subsystems.

With this change, the only known way of failing GO_ERROR is to try it in an inappropriate state, which can be ERROR (no point in transitioning from ERROR to ERROR) or DONE (too late, nothing to do).

Having to handle a failed GO_ERROR transition is something we should avoid. An interrupted GO_ERROR means that we might not perform the complete procedure and miss e.g. calling some services/subsystems.

With this change, the only known way of failing GO_ERROR is to try it in an inappropriate state, which can be ERROR (no point in transitioning from ERROR to ERROR) or DONE (too late, nothing to do).
@knopers8 knopers8 requested a review from justonedev1 October 30, 2025 07:49
@knopers8 knopers8 merged commit a9b1d25 into master Oct 30, 2025
1 check passed
@knopers8 knopers8 deleted the knopers8-patch-8 branch October 30, 2025 15:37
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.

2 participants