Skip to content

skip unchanged balances generation#85

Draft
gclaramunt wants to merge 2 commits intodevelopfrom
fix-balances
Draft

skip unchanged balances generation#85
gclaramunt wants to merge 2 commits intodevelopfrom
fix-balances

Conversation

@gclaramunt
Copy link
Contributor

No description provided.

@gclaramunt gclaramunt marked this pull request as draft January 28, 2026 20:20
Copy link

@ryle-ai ryle-ai left a comment

Choose a reason for hiding this comment

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

Review Summary

This PR has been open for ~9 months and now has merge conflicts with the develop branch.

Current Status

  • Merge State: CONFLICTING (cannot be merged as-is)
  • Last Activity: May 2025

Observations

1. Retry Logic May Be Partially Superseded

Commit 53c002b ("add retry #109") was merged to develop, which may have incorporated similar retry logic. Need to verify if this PR's retry implementation is still needed or if it duplicates existing functionality.

2. Key Concerns if Revived

If this PR is still relevant and will be rebased, please address:

  • Balance State Accumulation: The updateBalanceMap function merges only changed balances, but subsequent diff comparisons need full balance state. This could cause cascading incorrect diffs.

  • Inconsistency Between Full/Incremental: Full snapshots store complete balance maps, but incremental snapshots only store changes. This asymmetry may cause issues when processing alternates between snapshot types.

  • Unused balanceState Field: The new balanceState field in MetagraphData appears to be computed but never consumed downstream. Is this intended for future use?

  • Retry Mechanism: Only EofException is retried. Consider:

    • Adding exponential backoff
    • Handling other transient database errors
    • Adding delay between retries

Recommendation

Please either:

  1. Close this PR if the optimization is no longer needed or has been implemented differently
  2. Rebase against current develop and address the merge conflicts, then request re-review

Happy to do a thorough review of the updated code once conflicts are resolved.


Reviewed against snapshot-streaming codebase

Copy link

@ryle-ai ryle-ai left a comment

Choose a reason for hiding this comment

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

@gclaramunt just checking back in -- this has been open for a while now and the merge conflicts are still there. Is this something you're planning to pick back up, or would it make sense to close it out?

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