Skip to content

fix(dashmate): empty masternode status while syncing - #969

Closed
shuplenkov wants to merge 7 commits into
v0.24-devfrom
fix/dashmate_masternode_status
Closed

fix(dashmate): empty masternode status while syncing#969
shuplenkov wants to merge 7 commits into
v0.24-devfrom
fix/dashmate_masternode_status

Conversation

@shuplenkov

@shuplenkov shuplenkov commented Apr 24, 2023

Copy link
Copy Markdown

Issue being fixed or feature implemented

Dashmate status shows empty masternode status while syncing

What was done?

Dashmate status now shows UNKNOWN masternode status while it is syncing

How Has This Been Tested?

Manual

Breaking Changes

No

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@shuplenkov shuplenkov added this to the v0.24.0 milestone Apr 24, 2023
@shuplenkov shuplenkov closed this Apr 24, 2023
@shuplenkov
shuplenkov deleted the fix/dashmate_masternode_status branch April 24, 2023 17:12
llbartekll added a commit that referenced this pull request Aug 22, 2026
…arsing)

Pin fix/mnemonic-any-language-173ffac: the cherry-pick of
dashpay/rust-dashcore#980 onto 173ffac0, the rev v4.2-dev already pins.
This lands the BIP-39 fix without crossing the breaking key-wallet
sweep changes (rust-dashcore #961/#962/#966/#969) that #4406 adapts
platform to; once #4406 bumps onto rust-dashcore dev proper, the pin
rejoins dev and this branch can be deleted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
romchornyi pushed a commit that referenced this pull request Aug 22, 2026
…ashcore-dev-961

Two conflicts, both about the rust-dashcore pin, plus one semantic
break the textual merge hid.

`v4.2-dev` pinned `a97b32c6` in #4455, which turns out to be a side
branch off the old `173ffac0` carrying cherry-picks of the seed refresh
and the BIP-39 fix. This branch pinned `5877d15f`, on `dev`'s mainline.
Neither contains the other. Resolved onto `dev`'s head `b66db390`, which
is a superset of both: it carries the seed refresh (#970) and the BIP-39
fix (#980) that `v4.2-dev` wanted, plus #966 and #969 that this branch
needs, plus the QRInfo masternode-sync recovery (#947).

The hidden break: `v4.2-dev` added `get_wallet_blocking`, which calls
`blocking_read()` on the wallets map — a method this branch removed when
the map became an `ArcSwap`. Git merged the file cleanly and the build
failed. The accessor now loads wait-free; its name is kept so the FFI
callers that predate the change still compile.
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.

1 participant