Skip to content

chore(release): update changelog and bump version to 0.24.0-dev.22 - #945

Merged
shumkov merged 1 commit into
v0.24-devfrom
release_0.24.0-dev.22
Apr 20, 2023
Merged

chore(release): update changelog and bump version to 0.24.0-dev.22#945
shumkov merged 1 commit into
v0.24-devfrom
release_0.24.0-dev.22

Conversation

@shumkov

Copy link
Copy Markdown
Collaborator

Issue being fixed or feature implemented

Release new Dash Platform version

What was done?

  • Updated changelog
  • Bumped packages version

How Has This Been Tested?

None

Breaking Changes

None

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

@shumkov
shumkov requested a review from antouhou as a code ownerApril 20, 2023 11:16
@shumkovshumkov added this to the v0.24.0 milestone Apr 20, 2023
@shumkov
shumkov merged commit d0314db into v0.24-devApr 20, 2023
@shumkov
shumkov deleted the release_0.24.0-dev.22 branch April 20, 2023 11:17
romchornyi pushed a commit that referenced this pull request Aug 25, 2026
Per the decision on the blocker: the pinned branch is re-cut without
#866's `rescan_committed_range`.
Two reasons, and the second is the one that decides it. The Codex finding
stands — the sweep accumulates every match from the birth height into one
`BTreeMap` and queues them together, so an eclipsing compact-filter peer
can turn a full-history rescan into a chain-length allocation followed by
millions of block requests, and nothing upstream bounds it yet.
More decisive is the honest case. On a real long-history CoinJoined
restore the #846 backward sweep ran 191 times, reached a 2.9 GB
footprint, and was killed by jetsam before finishing; the coalescing fix
for that is dashpay/rust-dashcore#974, which is not merged. Shipping #866
without #974 would trade a mid-sync stall for a restore that kills the
app — and long-history migrated wallets are exactly this release's
audience.
What the pin still carries is the point of this PR: #964, #960, #955,
#947 and #946, the six sync-stall fixes, plus #945, #928, #963, #965,
#967, #970 and #980. Dropping #866 restores the status quo of the
previous pin rather than introducing a regression — #846's mid-sync
invisibility was never fixed in what shipped — and the migrated-wallet
heal (#4377) does a full rescan, so it does not lean on this sweep.
#866 and #974 come back together next cycle, with a bounded drain for the
accumulation finding.
Branch: dashpay/rust-dashcore@chore/sync-fixes-without-swept, re-cut at
33030acf (base #945 plus eight cherry-picks, #866 omitted).
Sign up for freeto 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.

2 participants

@shumkov@shuplenkov