-
Notifications
You must be signed in to change notification settings - Fork 101
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
feat: other core 21 updates #257
Conversation
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
f1df0d1
to
a12d1c3
Compare
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
* use auto close on a stream Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…HandlerTest Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…umRotationInfo Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
* add hashCode Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…dMasternodeListManager Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…State Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…fiedMasternodeListDiff Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…fiedMasternodeList Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
…blockchain Signed-off-by: HashEngineering <hashengineeringsolutions@gmail.com>
log.info("message = {}", lastRequest.getRequestMessage().toString(blockChain)); | ||
// This was causing a dead lock when using toString(DualBlockchain). Use toString() instead. | ||
log.info("message = {}", lastRequest.getRequestMessage()); |
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.
This was causing the stuck at 30-31%, a log.info call.
The lastRequest.getRequestMessage().toString(blockChain)
was taking a long time searching through blockChain
to find the block header to link a block hash to a height.
Now, we won't get the heights by calling the default toString()
.
Issue being fixed or feature implemented
What was done?
How Has This Been Tested?
QA using the Dash Wallet app
Breaking Changes
Some deprecated functions were removed.
Checklist:
For repository code-owners and collaborators only