Correct constant to HIGH_MAX_TX_FEE #517
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I noticed HIGH_MAX_TX_FEE is unused. There was probably an incorrect merge conflict resolution done previously; restore to the correct constant.
|
All failure of the latest bunch of PRs (at least from #509 and up) is due to timeout on It seems that the failure is due to PR 455. Testing |
ftrader
approved these changes
May 5, 2017
|
its pretty clear in all other portions of the code that maxTxFee.value is not used per-KB... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed HIGH_MAX_TX_FEE is unused. There was probably an incorrect
merge conflict resolution done previously; restore to the correct constant.