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

add parallel sync buffer as 1000 and will star to execute the block i… #4216

Closed
wants to merge 1 commit into from

Conversation

jackzhhuang
Copy link
Collaborator

@jackzhhuang jackzhhuang commented Sep 29, 2024

…f no absent block exists.

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Other information

Summary by CodeRabbit

  • New Features

    • Enhanced the block synchronization functionality to return a count of absent blocks, providing users with more detailed insights.
  • Bug Fixes

    • Improved handling of block absence conditions, ensuring more accurate processing during synchronization.

Copy link

coderabbitai bot commented Sep 29, 2024

Walkthrough

The pull request modifies the find_absent_ancestor function in the block_sync_task.rs file, changing its return type from Result<()> to Result<u64>. This allows the function to return a count of absent blocks instead of a simple success indication. The internal logic has been updated to track this count and return it appropriately. Additionally, the calling code has been adjusted to handle the new return type, affecting how absent blocks are processed.

Changes

File Change Summary
sync/src/tasks/block_sync_task.rs Updated find_absent_ancestor method signature to return Result<u64> instead of Result<()>. Introduced a count variable to track absent blocks and modified logic to return this count. Adjusted calling code to handle new return type.

Possibly related PRs

Suggested reviewers

  • sanlee42

Poem

In the code where blocks do play,
A count of absents found their way.
With each loop's turn, the tally grew,
A helpful change, both bright and new.
So hop along, let data flow,
For absent blocks, we now will know! 🐇✨

Warning

Review ran into problems

🔥 Problems

Error running Gitleaks: Command failed with exit code 4: jk_cp -o -f -k -j /cache/52/1cc2eb94-ff6c-413d-81b8-661342020586 /dev/null /dev/urandom /usr/bin/ast-grep /usr/bin/curl /usr/bin/diff /usr/bin/dirname /usr/bin/env /usr/bin/fd /usr/bin/gawk /usr/bin/gh /usr/bin/jq /usr/bin/patch /usr/bin/rg /usr/bin/shellcheck /usr/bin/tokei /usr/bin/tree /usr/bin/uniq /usr/bin/xargs /etc/ssl/certs /etc/passwd /etc/group /home/jailuser/ast-grep-rules

ERROR: /usr/bin/ast-grep does not exist

Usage: /usr/sbin/jk_cp -j [OPTIONS]

-h --help : this help screen
-j, --jail : the jail to copy to
-v, --verbose : show what is being copied
-f, --force : overwrite existing files
-k, --hardlink : use hardlinks if possible
-o, --owner : retain file ownership and group
-s, --setuid : retain file setuid/setgid bits

Note: if no jail is specified, the first argument is
considered to be the jail


Error running semgrep: Cloning the repository previously failed.


Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review.


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 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

@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: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a6f499b and ebf82d4.

📒 Files selected for processing (1)
  • sync/src/tasks/block_sync_task.rs (2 hunks)

Comment on lines +424 to +432
async fn find_absent_ancestor(&self, mut block_headers: Vec<BlockHeader>) -> Result<u64> {
let mut count: u64 = 0;
loop {
let mut absent_blocks = vec![];
self.find_absent_parent_dag_blocks_for_blocks(block_headers, &mut absent_blocks)?;
if absent_blocks.is_empty() {
return Ok(());
return Ok(count);
}
count = count.saturating_add(absent_blocks.len() as u64);
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Ensure correct handling of the new return type of find_absent_ancestor

The method find_absent_ancestor now returns Result<u64> instead of Result<()>. Within this file, ensure that all calls to this method correctly handle the new return value, and that the count of absent blocks is appropriately utilized.

Comment on lines +454 to +462
let count = self
.find_absent_ancestor(vec![block_header.clone()])
.await?;

if block_header.number() % 10000 == 0
if count == 0 {
return anyhow::Ok(ParallelSign::Continue);
}

if block_header.number() % 1000 == 0
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Assess the impact of changing the modulus condition from 10000 to 1000

The condition has changed from checking block_header.number() % 10000 == 0 to block_header.number() % 1000 == 0. This increases the frequency at which the associated code block executes. Review whether this change aligns with performance expectations and system requirements.

return anyhow::Ok(ParallelSign::Continue);
}

if block_header.number() % 1000 == 0
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: 这个可以改成一个常量参数

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ok.

@jackzhhuang jackzhhuang closed this Oct 9, 2024
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