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

fix: avoid extra work in GetListForBlockInternal before dip0003 activation #6527

Merged

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Jan 10, 2025

Issue being fixed or feature implemented

There could be no DMN before DIP0003, so let's bail out early. The result is less evodb reads and no initial snapshot spam in logs when syncing from scratch.

What was done?

How Has This Been Tested?

Breaking Changes

n/a

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

…ation

Less evodb reads, no `initial snapshot` spam in logs
@UdjinM6 UdjinM6 added this to the 22.1 milestone Jan 10, 2025
Copy link

coderabbitai bot commented Jan 10, 2025

Walkthrough

The pull request introduces a modification to the GetListForBlockInternal method in the CDeterministicMNManager class within the src/evo/deterministicmns.cpp file. The primary change involves adding a conditional check to verify the activation status of DIP0003 (a specific deployment) at a given block index. If DIP0003 is not active, the method now returns an empty CDeterministicMNList immediately, preventing further processing.

The modification alters the method's control flow by introducing an early exit condition based on the deployment status. The existing lock assertion (AssertLockHeld(cs)) has been repositioned to occur after the deployment check, ensuring it is only triggered if the method proceeds beyond the new conditional check. Additionally, comments have been added to improve code clarity and explain the purpose of the new conditional logic.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3edc738 and 82684ea.

📒 Files selected for processing (1)
  • src/evo/deterministicmns.cpp (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build Dependencies (linux64, x86_64-pc-linux-gnu)
  • GitHub Check: Build Dependencies (arm-linux, arm-linux-gnueabihf)
🔇 Additional comments (2)
src/evo/deterministicmns.cpp (2)

1030-1034: LGTM! Optimization to avoid unnecessary work.

The early exit for pre-DIP0003 blocks is a good optimization. It prevents unnecessary reads from evodb and eliminates irrelevant log entries during sync.


1035-1035: Verify the lock assertion placement.

Moving AssertLockHeld(cs) after the DIP0003 check is safe since:

  1. The check only reads immutable consensus parameters
  2. The early exit path doesn't access any shared state
  3. The lock is still verified before accessing any protected members

However, let's verify there are no subtle thread-safety issues by checking all callers.

✅ Verification successful

Lock assertion placement change is safe

The lock assertion can be safely moved after the DIP0003 check since all callers properly acquire the lock and the function's thread-safety requirements are correctly enforced through EXCLUSIVE_LOCKS_REQUIRED(cs).

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check all callers of GetListForBlockInternal to verify thread safety
# Test: Search for function calls. Expect: All callers should hold the lock.

# Find all calls to GetListForBlockInternal
rg "GetListForBlockInternal" -A 5 -B 5

# Find all lock acquisitions around those calls
rg "LOCK.*cs.*GetListForBlockInternal|GetListForBlockInternal.*LOCK.*cs" -A 5 -B 5

Length of output: 6144

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.

CDeterministicMNList snapshot;

if (!DeploymentActiveAt(*pindex, Params().GetConsensus(), Consensus::DEPLOYMENT_DIP0003)) {
Copy link
Collaborator

@knst knst Jan 11, 2025

Choose a reason for hiding this comment

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

should a similar check to be added also inside while(true) below?

pindex = pindex->pprev;
if (dip0003 is not activated) -> no need to read snapshot

Copy link
Author

Choose a reason for hiding this comment

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

As soon as dip3 is active we enter that loop and write/cache the initial snapshot. You can never go below this snapshot in that loop so we can be pretty sure dip3 is always active there.

Copy link
Collaborator

@knst knst left a comment

Choose a reason for hiding this comment

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

LGTM 82684ea

Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

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

utACK 82684ea

@PastaPastaPasta PastaPastaPasta merged commit 80cd18e into dashpay:develop Jan 16, 2025
25 checks passed
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.

3 participants