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

services/horizon: fix reingest duplicate errors on same ledger range #4114

Conversation

sreuland
Copy link
Contributor

@sreuland sreuland commented Dec 1, 2021

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    semver, or if it's mainly a patch change. The PR is targeted at the next
    release branch if it's not a patch change.

What

include liquidity pool tables in the ingest state machine's history operation purge for a given ledger range

Why

fix error during reingestion due to duplicate errors in liquidity pool table state

closes #4110

Known limitations

N/A

@sreuland sreuland requested a review from a team December 1, 2021 21:04
@sreuland sreuland force-pushed the 4110_reingest_liquidity_pool_dup_error branch from 33d9dae to 6572c6a Compare December 2, 2021 08:13
@tamirms tamirms changed the base branch from master to release-horizon-v2.12.0 December 2, 2021 09:04
@tamirms
Copy link
Contributor

tamirms commented Dec 2, 2021

@sreuland can you rebase on top of release-horizon-v2.12.0 and discard the commits which are not relevant?

@sreuland
Copy link
Contributor Author

sreuland commented Dec 2, 2021

@sreuland can you rebase on top of release-horizon-v2.12.0 and discard the commits which are not relevant?

@tamirms , how about I squash merge this down to one commit to release-horizon-v2.12.0, then I can port that commit to master afterwards?

@sreuland sreuland force-pushed the 4110_reingest_liquidity_pool_dup_error branch from 56e23bd to 6e88a58 Compare December 2, 2021 19:10
tt.NoError(horizoncmd.RootCmd.Execute())
tt.NoError(horizoncmd.RootCmd.Execute(), "Repeat the same reingest range against db, should not have errors.")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is the crux of change, verifies repeated ingest works over same range on same db.

@sreuland
Copy link
Contributor Author

sreuland commented Dec 2, 2021

@sreuland can you rebase on top of release-horizon-v2.12.0 and discard the commits which are not relevant?

@tamirms , how about I squash merge this down to one commit to release-horizon-v2.12.0, then I can port that commit to master afterwards?

@tamirms , I rebased to the release branch and squashed, should be finished in CI soon, thanks!

@tamirms
Copy link
Contributor

tamirms commented Dec 2, 2021

great, thanks! I will merge

@tamirms tamirms merged commit e560a90 into stellar:release-horizon-v2.12.0 Dec 2, 2021
sreuland added a commit to sreuland/go that referenced this pull request Dec 2, 2021
sreuland added a commit to sreuland/go that referenced this pull request Aug 7, 2022
sreuland added a commit to sreuland/go that referenced this pull request Aug 7, 2022
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.

Horizon db reingest command has duplicate error when run multiple times with same ledger range
2 participants