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/internal/expingest/processors: Only process authorized trustlines when updating asset stats #1936

Merged
merged 2 commits into from
Nov 15, 2019

Conversation

tamirms
Copy link
Contributor

@tamirms tamirms commented Nov 15, 2019

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

The experimental ingestion pipeline has a bug in that it counts unauthorized trustlines when computing asset stats. Only authorized trustlines should be included.

Another issue fixed in this PR is that the cursor for the new asset stats endpoint diverges from the existing asset stats endpoint

Close #1933

Why

The new asset stats endpoint should have identical semantics to the existing endpoint

The paging token for the asset stats rows used by the legacy ingestion system was formatted as:
BTC_GB7ZHXCNHG5IMEHIS2MG54DR3QJIPAQIBFBKZDMCHSDLJYNJNZXKS4SO_credit_alphanum4

The experimental ingestion system used a format of:
BTC:GB7ZHXCNHG5IMEHIS2MG54DR3QJIPAQIBFBKZDMCHSDLJYNJNZXKS4SO
@cla-bot cla-bot bot added the cla: yes label Nov 15, 2019
@tamirms tamirms requested review from bartekn and abuiles November 15, 2019 16:11
@bartekn bartekn merged commit d222515 into stellar:release-horizon-v0.23.0 Nov 15, 2019
bartekn added a commit that referenced this pull request Nov 15, 2019
Bumps `expingest.CurrentVersion` to recreate state due to a bug fixed in
#1936. We need to reingest existing state due to a rules change
connected to trust lines authorization.
err := set.Add(xdr.TrustLineEntry{
AccountId: xdr.MustAddress("GAOQJGUAB7NI7K7I62ORBXMN3J4SSWQUQ7FOEPSDJ322W2HMCNWPHXFB"),
Asset: xdr.MustNewCreditAsset("EUR", trustLineIssuer.Address()),
Balance: 1,
Copy link
Contributor

Choose a reason for hiding this comment

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

I think passing Flags: 0 instead of relying on the zero value could help making the test more explicit about the expectations and how the trustline entry should look like.

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.

3 participants