Skip to content

feat: added flush of parity-db logs after block import#1219

Open
Klapeyron wants to merge 2 commits intomainfrom
feat/ledger_enact_parity_db_logs
Open

feat: added flush of parity-db logs after block import#1219
Klapeyron wants to merge 2 commits intomainfrom
feat/ledger_enact_parity_db_logs

Conversation

@Klapeyron
Copy link
Copy Markdown
Contributor

Overview

🗹 TODO before merging

  • Ready

📌 Submission Checklist

  • Changes are backward-compatible (or flagged if breaking)
  • Pull request description explains why the change is needed
  • Self-reviewed the diff
  • I have included a change file, or skipped for this reason:
  • If the changes introduce a new feature, I have bumped the node minor version
  • Update documentation (if relevant)
  • Updated AGENTS.md if build commands, architecture, or workflows changed
  • No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

  • Additional tests are provided (if possible)

🔱 Fork Strategy

  • Node Runtime Update
  • Node Client Update
  • Other:
  • N/A

Links

@Klapeyron Klapeyron self-assigned this Apr 1, 2026
@Klapeyron Klapeyron requested a review from a team as a code owner April 1, 2026 21:29
@Klapeyron Klapeyron changed the title feat: added flush of parity-db logs after own block import feat: added flush of parity-db logs after block import Apr 1, 2026
@Klapeyron Klapeyron force-pushed the feat/ledger_enact_parity_db_logs branch from 8042521 to 5e0c28a Compare April 1, 2026 21:46
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.

1 participant