Skip to content

cre-5476: extra recovery#23130

Open
mchain0 wants to merge 1 commit into
developfrom
cre-5476
Open

cre-5476: extra recovery#23130
mchain0 wants to merge 1 commit into
developfrom
cre-5476

Conversation

@mchain0

@mchain0 mchain0 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@mchain0
mchain0 requested a review from a team as a code owner July 15, 2026 11:46
@github-actions

Copy link
Copy Markdown
Contributor

👋 mchain0, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@github-actions

Copy link
Copy Markdown
Contributor

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@cl-sonarqube-production

Copy link
Copy Markdown

@trunk-io

trunk-io Bot commented Jul 15, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

@mchain0
mchain0 requested a review from jmank88 July 15, 2026 12:16
Comment on lines +170 to +173
if r := recover(); r != nil {
err = fmt.Errorf("workflow module execution panicked: %v", r)
e.logger().Errorw("Recovered from panic during workflow module execution", "err", err, "stack", string(debug.Stack()))
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Arbitrary recovers are not safe. The node may be in a bad state. If we need to recover in order to record the result and prevent a boot loop, that may be OK, but it is important to rethrow the panic afterwards so that we get a full reset from the reboot, rather than continuing in an unknown state.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

pm

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