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

exp/orderbook: Fix bug in strict send path finding search #1863

Merged
merged 1 commit into from
Oct 21, 2019

Conversation

tamirms
Copy link
Contributor

@tamirms tamirms commented Oct 21, 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.

Summary

There is a bug in consumeOffersForBuyingAsset() which manifests when currentAssetAmount is not high enough to purchase the selling asset. In such cases consumeOffersForBuyingAsset() should return -1, nil but because of the bug the function returns a positive amount with no error.

Fixes #1856

There is a bug in `consumeOffersForBuyingAsset()` which manifests when `currentAssetAmount` is not high enough
to purchase the selling asset. In such cases `consumeOffersForBuyingAsset()` should return -1, nil but because of the bug
the function would return a positive amount with no error
@tamirms tamirms requested a review from bartekn October 21, 2019 13:55
@cla-bot cla-bot bot added the cla: yes label Oct 21, 2019
return totalConsumed, nil
}
if currentAssetAmount < 0 {
return -1, errSoldTooMuch
Copy link
Contributor

Choose a reason for hiding this comment

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

Here and in other places where we return errSoldTooMuch: doesn't it result in 500 Internal Server Error returned? Shouldn't we skip the path and continue with the next one instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

errSoldTooMuch should never happen. If it does then there is a bug in price.ConvertToBuyingUnits or some other part of the code

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, then isn't there a bug somewhere else if this happened in #1856?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

correct, the the bug isn't in this function. I just added this check as a precaution.

The bug is in consumeOffersForBuyingAsset() when amountSold is 0 and err is nil in:

amountSold, err := price.MulFractionRoundDown(int64(currentAssetAmount), d, n)

Copy link
Contributor

Choose a reason for hiding this comment

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

I can see it now, thanks!

@tamirms tamirms merged commit 739f165 into stellar:release-horizon-v0.23.0 Oct 21, 2019
@tamirms tamirms deleted the strict-send-fix branch October 21, 2019 15:25
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