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

Use the same block executor for both CAPI and StagedSync #2307

Merged
merged 11 commits into from
Sep 12, 2024

Conversation

bzawisto
Copy link
Contributor

@bzawisto bzawisto commented Sep 5, 2024

No description provided.

@bzawisto bzawisto marked this pull request as draft September 5, 2024 12:25
@bzawisto bzawisto marked this pull request as ready for review September 10, 2024 15:00
@canepat canepat changed the title Use the same block executor for both CAPI and StagegSync Use the same block executor for both CAPI and StagedSync Sep 10, 2024
@canepat canepat added the maintenance Some maintenance work (fix, refactor, rename, test...) label Sep 10, 2024
using namespace std::chrono_literals;

//! Generate log arguments for execution progress at specified block
static log::Args log_args_for_exec_progress(BlockExecutor::ExecutionProgress& progress, uint64_t current_block) {
Copy link
Member

Choose a reason for hiding this comment

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

This logging format is specifically crafted for Erigon++ to match Erigon logs and must be kept into the C API implementation. The stage pipeline has its own timer-based logging mechanism that must remain the same because it's shared among all the stages.

log::Info{"[4/12 Execution] Executed blocks", // NOLINT(*-unused-raii)
log_args_for_exec_progress(progress_, block.header.number)};
log_time_ = now + 20s;
}
Copy link
Member

Choose a reason for hiding this comment

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

This logging format is specifically crafted for Erigon++ to match Erigon logs and must be kept into the C API implementation. The stage pipeline has its own timer-based logging mechanism that must remain the same because it's shared among all the stages.

@bzawisto bzawisto requested a review from canepat September 11, 2024 17:08
@canepat canepat merged commit 1da9551 into master Sep 12, 2024
5 checks passed
@canepat canepat deleted the 2078-execution-improve-stage-execution branch September 12, 2024 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Some maintenance work (fix, refactor, rename, test...)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

execution: improve stage Execution according to C API execute functions
3 participants