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

Fix error message returned by EstimateFee #1678

Merged
merged 1 commit into from
Feb 9, 2021

Conversation

Appelberg-s
Copy link
Contributor

When you provide an argument to EstimateFee(numblocks uint32) that exceeds the estimateFeeDepth (which is set to 25), you get an error message that says "can only estimate fees for up to 100 blocks from now". The variable used in the if condition and the variable used for creating the error message should be the same.

When you provide an argument to EstimateFee(numblocks uint32) that exceeds the estimateFeeDepth (which is set to 25), you get an error message that says "can only estimate fees for up to 100 blocks from now".  The variable used in the if condition and the variable used for creating the error message should be the same.
@coveralls
Copy link

coveralls commented Feb 4, 2021

Pull Request Test Coverage Report for Build 538681709

  • 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.03%) to 53.436%

Changes Missing Coverage Covered Lines Changed/Added Lines %
mempool/estimatefee.go 0 1 0.0%
Files with Coverage Reduction New Missed Lines %
peer/peer.go 2 76.18%
Totals Coverage Status
Change from base Build 535940167: 0.03%
Covered Lines: 20864
Relevant Lines: 39045

💛 - Coveralls

Copy link
Member

@jcvernaleo jcvernaleo left a comment

Choose a reason for hiding this comment

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

Nice catch.

OK

@jcvernaleo jcvernaleo merged commit dff2198 into btcsuite:master Feb 9, 2021
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.

4 participants