-
Notifications
You must be signed in to change notification settings - Fork 501
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: Correctly check trustline flags to classify asset balances #3847
services/horizon: Correctly check trustline flags to classify asset balances #3847
Conversation
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.
LGTM! We also need to bump ingest.CurrentVersion
to trigger state rebuild. Also I wonder if should merge it into master or a branch based on horizon-v2.8.0
. Release branch is not merged yet so it's hard to tell what else is there that'd require testing.
c18fa8b
to
5255fb3
Compare
5255fb3
to
63916f2
Compare
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.
Just making sure: Targeting the release-horizon-v2.8.0
branch is intentional, right?
…alances (#3847) * use method accessors for asset stats amount classification * Update changelog * bump ingest.CurrentVersion * Fix up test Post rebase
…alances (#3847) * use method accessors for asset stats amount classification * Update changelog * bump ingest.CurrentVersion * Fix up test Post rebase
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
Use the method accessors to check which flags are set on a trustline.
Why
Fixes #3846
Direct byte-comparison misses combination flags, e.g.
TrustLineAuthorized | TrustLineClawbackEnabled
, and classifies them asunauthorized
.Known limitations
[TODO or N/A]