-
Notifications
You must be signed in to change notification settings - Fork 499
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
services/horizon: fix reingest duplicate errors on same ledger range #4114
Conversation
33d9dae
to
6572c6a
Compare
@sreuland can you rebase on top of release-horizon-v2.12.0 and discard the commits which are not relevant? |
…te issue on liquidity pool tables(stellar#4114)
56e23bd
to
6e88a58
Compare
tt.NoError(horizoncmd.RootCmd.Execute()) | ||
tt.NoError(horizoncmd.RootCmd.Execute(), "Repeat the same reingest range against db, should not have errors.") |
There was a problem hiding this comment.
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.
@tamirms , I rebased to the release branch and squashed, should be finished in CI soon, thanks! |
great, thanks! I will merge |
…te issue on liquidity pool tables(stellar#4114)
…te issue on liquidity pool tables(stellar#4114)
…te issue on liquidity pool tables(stellar#4114)
PR Checklist
PR Structure
otherwise).
services/friendbot
, orall
ordoc
if the changes are broad or impact manypackages.
Thoroughness
.md
files, etc... affected by this change). Take a look in the
docs
folder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
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