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

Start submitting misbehavior reports #414

Open
wants to merge 1 commit into
base: 01-15-add_loggingmisbehaviorservice
Choose a base branch
from

Conversation

neekolas
Copy link
Contributor

@neekolas neekolas commented Jan 15, 2025

TL;DR

Added misbehavior reporting for out-of-order envelopes in the sync worker.

What changed?

  • Integrated a misbehavior service into the sync worker
  • Added logic to create and submit safety failure reports when out-of-order envelopes are detected
  • Enhanced error handling with detailed logging for misbehavior report creation and submission failures

How to test?

  1. Set up two nodes in a sync relationship
  2. Deliberately send out-of-order envelopes from one node
  3. Verify that misbehavior reports are generated and logged
  4. Check logs for any report creation or submission errors

Why make this change?

To improve network reliability by tracking and reporting out-of-order envelope submissions, which could indicate node misbehavior or network issues. This helps maintain the integrity of message ordering and enables better monitoring of node behavior.

Summary by CodeRabbit

  • New Features

    • Enhanced error handling for out-of-order envelope processing
    • Added formal misbehavior reporting mechanism for sync operations
  • Improvements

    • Integrated advanced tracking of synchronization anomalies
    • Improved error detection and logging for envelope validation

Copy link

coderabbitai bot commented Jan 15, 2025

Walkthrough

The changes introduce misbehavior reporting functionality to the syncWorker in the synchronization package. A new misbehaviorService field is added to the syncWorker struct, allowing the tracking and reporting of out-of-order envelope issues. The validateAndInsertEnvelope method is enhanced to use this service, replacing simple error logging with a formal misbehavior reporting mechanism. A new submitOutOfOrderReport method is implemented to encapsulate the logic for creating and submitting safety failure reports.

Changes

File Change Summary
pkg/sync/syncWorker.go - Added misbehaviorService field of type misbehavior.MisbehaviorService
- Modified startSyncWorker to initialize misbehavior service
- Updated validateAndInsertEnvelope to use submitOutOfOrderReport
- Added new method submitOutOfOrderReport for creating misbehavior reports

Sequence Diagram

sequenceDiagram
    participant SW as SyncWorker
    participant MS as MisbehaviorService
    participant ENV as Envelope

    SW ->> SW: Receive Envelope
    alt Out-of-Order Envelope Detected
        SW ->> SW: Create Safety Failure Report
        SW ->> MS: submitOutOfOrderReport()
        MS -->> SW: Report Submitted
    else Normal Envelope
        SW ->> SW: Process Normally
    end
Loading

Finishing Touches

  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@neekolas neekolas force-pushed the 01-15-start_submitting_misbehavior_reports branch from 68175fe to d8b159f Compare January 15, 2025 20:02
@neekolas neekolas marked this pull request as ready for review January 15, 2025 20:04
@neekolas neekolas requested a review from a team as a code owner January 15, 2025 20:04
@neekolas neekolas force-pushed the 01-15-add_loggingmisbehaviorservice branch from c5226fd to 6443a91 Compare January 15, 2025 20:07
@neekolas neekolas force-pushed the 01-15-start_submitting_misbehavior_reports branch from d8b159f to d3f2f32 Compare January 15, 2025 20:07
@neekolas neekolas force-pushed the 01-15-add_loggingmisbehaviorservice branch from 6443a91 to 7666a1b Compare January 15, 2025 20:09
@neekolas neekolas force-pushed the 01-15-start_submitting_misbehavior_reports branch from d3f2f32 to 0319ff8 Compare January 15, 2025 20:09
@@ -362,8 +365,19 @@ func (s *syncWorker) validateAndInsertEnvelope(
lastNs = stream.lastEnvelope.OriginatorNs()
}
if env.OriginatorSequenceID() != lastSequenceID+1 || env.OriginatorNs() < lastNs {
// TODO(rich) Submit misbehavior report and continue
s.log.Error("Received out of order envelope")
if report, err := misbehavior.NewSafetyFailureReport(
Copy link
Collaborator

Choose a reason for hiding this comment

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

I really struggle to read this inlined error handling. We generally don't use the format.

The explicit formatting is much more readable:

report, err := misbehavior.NewSafetyFailureReport(
    stream.nodeID,
    message_api.Misbehavior_MISBEHAVIOR_OUT_OF_ORDER,
    true,
    []*envUtils.OriginatorEnvelope{stream.lastEnvelope, env},
)
if err != nil {
    // Log the error if the report creation fails
    s.log.Debug("Failed to create misbehavior report", zap.Error(err))
    return // Exit early or handle it as appropriate
}

// Submit the misbehavior report
err = s.misbehaviorService.SafetyFailure(report)
if err != nil {
    // Log the error if the report submission fails
    s.log.Debug("Failed to submit misbehavior report", zap.Error(err))
}

Copy link
Contributor Author

@neekolas neekolas Jan 17, 2025

Choose a reason for hiding this comment

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

Fair enough. I don't love the double nesting here.

I'll move to its own function so that I can early return, since this whole code path is optional

@neekolas neekolas force-pushed the 01-15-start_submitting_misbehavior_reports branch from 0319ff8 to 0b49138 Compare January 17, 2025 15:42
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
pkg/sync/syncWorker.go (1)

63-71: Consider making misbehaviorService configurable.

Currently, the service is hardcoded to use a logging implementation. Consider making it configurable through the constructor to improve testability and flexibility.

 func startSyncWorker(
 	ctx context.Context,
 	log *zap.Logger,
 	nodeRegistry registry.NodeRegistry,
 	registrant *registrant.Registrant,
 	store *sql.DB,
+	misbehaviorService misbehavior.MisbehaviorService,
 ) (*syncWorker, error) {
 	ctx, cancel := context.WithCancel(ctx)
+	if misbehaviorService == nil {
+		misbehaviorService = misbehavior.NewLoggingMisbehaviorService(log)
+	}
 	s := &syncWorker{
 		ctx:                ctx,
 		log:                log.Named("syncWorker"),
 		nodeRegistry:       nodeRegistry,
 		registrant:         registrant,
 		store:              store,
 		wg:                 sync.WaitGroup{},
 		subscriptions:      make(map[uint32]struct{}),
 		cancel:             cancel,
-		misbehaviorService: misbehavior.NewLoggingMisbehaviorService(log),
+		misbehaviorService: misbehaviorService,
 	}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7666a1b and 0b49138.

📒 Files selected for processing (1)
  • pkg/sync/syncWorker.go (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Graphite / mergeability_check
  • GitHub Check: Test (Node)
  • GitHub Check: Graphite / mergeability_check
🔇 Additional comments (2)
pkg/sync/syncWorker.go (2)

15-15: LGTM! Clean integration of misbehavior reporting.

The new import and field addition are well-structured and align with the PR objectives.

Also applies to: 35-35


368-371: LGTM! Good error handling approach.

The error handling is clean and follows the feedback from previous reviews. Appropriately continues processing even if report submission fails.

pkg/sync/syncWorker.go Show resolved Hide resolved
@neekolas neekolas requested a review from mkysel January 17, 2025 15:48
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