-
Notifications
You must be signed in to change notification settings - Fork 65
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
Core Improvements and Bugfixes #89
Core Improvements and Bugfixes #89
Conversation
This will be needed to postpone difficulty adjustment modifications to a block in the future throughout the functional tests
…sqlite warning message in DigiByte Core
…, CORE: increased peer timeouts
…ady being tracked' error
…get support for BIP68
… functional test)
…empool, even if they were not supposed to
…tocol consensus from 70016 to 70018
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.
ACK. Awesome work @SmartArray! This seems to finally have eliminated the crash bug with dandelion. Going commit by commit it all looks good. The client compiles, runs, and works as expected. One question I had was the commit about DEFAULT_MIN_RELAY_TX_FEE = 100000. Thats 1/100 of a DGB. Should we make it 1/10?
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.
ACK
Excellent work on this @SmartArray ! It is absolutely refreshing to be so much closer to having the functional test suite fully operational. I'm looking forward to review #90 !
So it was this legacy code that was causing a transaction to effectively be removed twice? However this identical code appears in the 0.17 branch as well: |
Receive this on feature/8.22.0 with pull request #89 applied (note that digibyted itself is fine). |
If you remove the additional primitives/block.cpp added to the Makefile.am:
and instead make this change to Makefile.am:
It will compile correctly with no symbol errors. |
Upon running unit tests:
|
Thank you @barrystyle for testing this. Yes, I think this is the correct way to deal with the linking error. There were several issues regarding the mempool. And yes, the code you highlighted was absolutely in there before. That would explain why reorgs caused the client to misbehaving on occasion. Again, thank you for checking this 🙂 I will apply and check the fix soon! |
Found that too. This is because I had to change some network params |
Previous change to Makefile.am caused Linking issue on Debian based systems.
Hey guys, please try to |
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.
ACK Happy with these changes
@barrystyle Thanks for the review. Are you able to do PR 90? |
Very strong work @SmartArray ! Thank you for all your hard effort here. |
can do. |
Core Improvements and Bugfixes
This PR fixes several bugs that were detected by fixing the functional tests. Those fixes include for instance
generatetoaddress
,difficulties
)easypow
parameter for RegTestWTXID
protocol command