Skip to content

chore(code): Move mode check for effect handling in engine #942

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

Draft
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

ancazamfir
Copy link
Collaborator

Closes: #XXX


PR author checklist

For all contributors

For external contributors

Copy link

codecov bot commented Mar 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (5fb4820) to head (23c5a2b).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@     Coverage Diff     @@
##   main   #942   +/-   ##
===========================
===========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ancazamfir ancazamfir changed the title chore(code): Move mode check on effect handling in engine chore(code): Move mode check for effect handling in engine Mar 25, 2025
@ancazamfir ancazamfir marked this pull request as ready for review March 25, 2025 16:08
@ancazamfir ancazamfir requested a review from romac as a code owner March 25, 2025 16:08
Comment on lines 957 to 960
let should_broadcast = match &msg {
SignedConsensusMsg::Vote(_) => true,
_ => value_payload.include_proposal(),
};
Copy link
Member

Choose a reason for hiding this comment

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

Let's refactor this into a function that we can use here and for the WAL below

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think for the WAL we will have to remove the check when we fix #897. So we have three options

Copy link

github-actions bot commented Apr 28, 2025

✅ Semver Check Passed

Great job! All semver violations have been resolved. This PR now complies with semantic versioning rules.

If you made version updates, please ensure that:

  • The version in Cargo.toml accurately reflects the nature of your changes
  • Any breaking changes are properly documented in BREAKING_CHANGES.md

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