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

chore(starknet_consensus_orchestrator): add function to await the second proposal part message #4043

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

matan-starkware
Copy link
Contributor

No description provided.

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Contributor

@asmaastarkware asmaastarkware left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @matan-starkware)


crates/starknet_consensus_orchestrator/src/sequencer_consensus_context.rs line 773 at r1 (raw file):

    let mut content = Vec::new();
    let deadline = tokio::time::Instant::now() + timeout;
    // Validating first proposal part, it should be fin in case this is an empty proposal,

assuming first part is the init

Suggestion:

// Validating the second proposal part, it should be fin in case this is an empty proposal,

crates/starknet_consensus_orchestrator/src/sequencer_consensus_context.rs line 886 at r1 (raw file):

                }
                x => {
                    warn!("Invalid second proposal part: {x:?}");

I agree to warn on invalid proposal parts instead of panicking 👍

Copy link
Contributor Author

@matan-starkware matan-starkware left a comment

Choose a reason for hiding this comment

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

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @asmaastarkware)


crates/starknet_consensus_orchestrator/src/sequencer_consensus_context.rs line 773 at r1 (raw file):

Previously, asmaastarkware (asmaa-starkware) wrote…

assuming first part is the init

I just moved the comment to the fn definition

@matan-starkware matan-starkware force-pushed the matan/m15/await_second_proposal_part branch from 9fb7a0b to 4315a47 Compare February 10, 2025 13:23
Copy link
Contributor

@asmaastarkware asmaastarkware left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @matan-starkware)

@matan-starkware matan-starkware force-pushed the matan/m15/await_second_proposal_part branch from 4315a47 to cf0b8c9 Compare February 10, 2025 16:02
Copy link
Contributor Author

matan-starkware commented Feb 11, 2025

Merge activity

  • Feb 11, 2:27 AM EST: A user started a stack merge that includes this pull request via Graphite.
  • Feb 11, 2:27 AM EST: A user added this pull request to the GitHub merge queue with Graphite.

@matan-starkware matan-starkware added this pull request to the merge queue Feb 11, 2025
Merged via the queue into main with commit 957059f Feb 11, 2025
9 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants