* instantsend: Use `NotifyEntryRemoved` signal instead of calling `CInstantSendManager::TransactionRemovedFromMempool` from `CTxMemPool::removeUnchecked` directly
Fixes potential mempool.cs vs cs_main (in RemoveConflictingLock) deadlock
* Apply suggestions from code review
yay, typso!
Co-authored-by: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
Co-authored-by: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
* instantsend: Upgrade IS db on dip0020 activation
* instantsend: Do not remove islocks for txes removed from mempool until dip0020 is activated
* refactor: introduce fUpgradedDB to avoid excessive locking and checking the state
* llmq: Decouple `fUpgradedDB` from `cs`
* Update src/llmq/quorums_instantsend.cpp
Co-authored-by: dustinface <35775977+xdustinface@users.noreply.github.com>
* Fix deadlock
Upgrade locks cs_main via GetTransaction
Co-authored-by: xdustinface <xdustinfacex@gmail.com>
Co-authored-by: dustinface <35775977+xdustinface@users.noreply.github.com>
* instantsend: Resolve block conflicts first and take care of mempool ones later
* refactor: Rename RemoveChainLockConflictingLock -> RemoveConflictingLock
* instantsend: Handle transaction removal from mempool (for all reasons besides inclusion in blocks)
* instantsend: Remove old islocks with no known txes from db (once)
* refactor: Replace magic number with CURRENT_VERSION
* fix: Do not remove islocks for (yet) valid orphans
* Apply suggestions from code review
Co-authored-by: dustinface <35775977+xdustinface@users.noreply.github.com>
Co-authored-by: dustinface <35775977+xdustinface@users.noreply.github.com>
* evo: Remove all protx-es that refer to a ProRegTx removed from mempool
* tests: Check that removal of ProRegTx causes removal of other protx-es that refer to it
* evo: Consider tx itself a collateral in mempool maps when payload collateral hash is null
* tests: Should not allow a ProRegTx which uses another ProRegTx as an external collateral to enter mempool
Signed-off-by: pasta <pasta@dashboost.org>
* tests: Check that CLs override ISes which invalidated non-CLed blocks earlier
* partial revert 3987: Do not mark blocks which conflict with ISes as "conflicting"
* evo: Refactor (Add/Update/Remove)MNs to do the job in one go
Instead of hashing the value and querying `mnUniquePropertyMap` both 2 or 3 times per property.
Also unify their error messages while at it.
* evo: Align nullValue checks with others in {Add|Delete}UniqueProperty
Co-authored-by: xdustinface <xdustinfacex@gmail.com>
* qt: Add missing -font-family overridden check
* qt: Add missing `QFont::ExtraBold`
* qt: Remove settings depencency from GUIUtil::loadFonts and load earlier
* qt: Modify supportedWeightToIndex
Return -1 in case of failure
* qt: Add GUIUtil::isSupportedWeight
* qt: Make sure there are always supported weights in the settings
* qt: Add "supported defaults" + store weights based on font family
* qt: Use supported defaults in update weight sliders
* qt: Use supported defaults when updating weight sliders
* qt: Fix tests
* qt: Apply themes globally
And do this early
* qt: Fix unexpected prompt icon in dash themes
This has been introduced by removing the `GUIUtil::loadStyleSheet(node,
autoCompleter->popup());` call which triggered a `QEvent::StyleChange`
to propery load the widgets before.
* qt: Move custom css timer out of loadStyleSheet
Co-authored-by: xdustinface <xdustinfacex@gmail.com>
* qt: Always use predefined css filenames instead of guessing them when using custom css dir
* qt: Safer getActiveTheme
* qt: Use correct default theme in dashThemeActive
3a03d2a33f Qt: load wallet in UI after possible init aborts (Jonas Schnelli)
Pull request description:
Bug was introduced in #13063 (80b4910f7d87983f50047074c3c2397b0a5c4e92) where #13097 made possible to get "hit" by that bug. Reported by @ken2812221 (https://github.com/bitcoin/bitcoin/pull/13097#issuecomment-398445833).
Dynamically loading a wallet informs the UI (and therefore makes the instance accessible) about the new wallet before all possible error cases where handled.
Easy to reproduce by starting `bitcoin-qt --regtest --nowallet -usehd=0` then in the console enter `loadwallet wallet.dat`.
This PR will make sure only correctly initialised (loaded) wallets will appear in the UI.
Tree-SHA512: 3139545e852d53b117182b579f45259c198d1c25c1a6fa4e0108f942d45f6fe2691e6bfcbbae2e18c33ad0174a520f379c17867b1eb87f950d830a5f519fec4f