Skip to content

feat: implement ledger-range export generator#947

Open
ifygreg01-best wants to merge 2 commits into
Pulsefy:mainfrom
ifygreg01-best:feat/ledger-range-export-883
Open

feat: implement ledger-range export generator#947
ifygreg01-best wants to merge 2 commits into
Pulsefy:mainfrom
ifygreg01-best:feat/ledger-range-export-883

Conversation

@ifygreg01-best

Copy link
Copy Markdown

Summary

Adds a ledger-range export generator to the data-processing service to aid maintainers during incident debugging.

Changes

  • src/ledger_export.pyLedgerRangeExporter class: validates range, exports raw ContractEvent rows and normalized ProjectView/ProjectContributor/ProjectMilestone state into a single deterministic JSON file
  • scripts/export_ledger_range.py — CLI entry point
  • tests/test_ledger_export.py — 20 tests (all passing)
  • scripts/README_ledger_export.md — documentation

Export format

{
  "metadata": { "startLedger": 1000, "endLedger": 2000, "exportTimestamp": "...", "exportVersion": "1" },
  "raw": [...],
  "normalized": { "project_views": [...], "project_contributors": [...], "project_milestones": [...] }
}

Testing

All 20 new tests pass. No regressions in existing suite.

Closes #883

@drips-wave

drips-wave Bot commented Jun 25, 2026

Copy link
Copy Markdown

@ifygreg01-best Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@Cedarich

Copy link
Copy Markdown
Contributor

@ifygreg01-best fix ci

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.

Data-processing: Ledger-range export generator for incident debugging

2 participants