-
Notifications
You must be signed in to change notification settings - Fork 59
fix(swift-sdk): stop born-spent TXO rows at the persistence seam and reconcile the store after a full scan #4638
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
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
c098ac1
feat(platform-wallet): carry the engine's credit verdicts through the…
llbartekll b6197b6
fix(swift-sdk): write born-spent TXO rows spent, and reconcile the st…
llbartekll d7515ac
test(swift-sdk): verify the credit-verdict seam and the store reconcile
llbartekll e71f639
fix(platform-wallet, swift-sdk): durable evidence only — merge, class…
llbartekll d478786
Merge remote-tracking branch 'origin/v4.2-dev' into fix/swift-sdk-txo…
llbartekll 7ce3573
fix(platform-wallet-ffi): report a failing credit-verdict slot throug…
llbartekll b19989b
fix(platform-wallet, swift-sdk): decide heal eligibility in the engin…
llbartekll f8e8460
chore: pin rust-dashcore to integration/v4.2-pin-plus-989 (current pi…
llbartekll a74e78b
fix(platform-wallet-ffi, swift-sdk): degrade unmappable tags to Unkno…
llbartekll 0b77da9
fix(platform-wallet, swift-sdk): judge verdicts on one snapshot, guar…
llbartekll da84e31
fix(platform-wallet): drop the test-only slices wrapper, copy `Output…
llbartekll 2b61dca
fix(swift-sdk, platform-wallet): fail the heal on an unreadable accou…
llbartekll 0b87b4b
fix(swift-sdk): a failed TXO lookup fails the reconcile step instead …
llbartekll File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 pins the whole workspace to a throwaway branch that is now behind
dev, and rolls four merged fixes back in the process.All eight dependencies move from
93260bf3to697bfb72. I checked that rev againstrust-dashcore:dev—dev...697bfb72isdiverged, ahead=1, behind=5, and the only branch whose head it is isintegration/v4.2-pin-plus-989.697bfb72 fix(dash-spv): stop losing derived scripts, and close the loop on wallet state— the pre-merge version of fix(dash-spv): stop losing derived scripts, and close the loop on wallet state rust-dashcore#989. That PR merged intodevtoday ase4208c90, so the reason this integration branch exists is already gone.#1000(ask every account whether a transaction is new),#1005(build!: adopt GroveDB bincode across the workspace— a breaking build change),#1001(keep a spend-first coin recognisable) and#1004(discover DashPay asset unlock receipts).So merging as-is ties platform to a branch nothing else references and moves the pin backwards relative to
dev, including across abuild!change. Re-pinning to adevrev gets #989 and the other four together.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.
The rev is behind
dev, but it does not roll anything back relative to platform:v4.2-devpins93260bf3, which already lacks #1000, #1001, #1004 and #1005;697bfb72is exactly that pin plus #989. Pinning to adevrev is what the PR wants too, and it is blocked: #1005 (GroveDB bincode,build!) landed ondevbefore #989, so everydevrev that has #989 also has #1005, which platform cannot build until #4635 merges. The PR body states the plan: the integration branch is a stand-in until #4635 lands, then the pin moves todevand the branch is deleted. If you would rather this PR not touch the pin at all and leave the bump to #4635/#4627, that is a one-commit revert; leaving the decision with @llbartekll.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.
Decision: staying on the integration branch. Without #989 this fix does not work end to end on the device (the engine drops the spending blocks), so the PR has to carry it, and no
devrev can be pinned until #4635 lands. Once it does, the pin moves todevin a follow-up andintegration/v4.2-pin-plus-989is deleted; that step is tracked in the PR body.