[sui-rpc-api][sui-kv-rpc] refactor Resolved*Range.apply_cursor_bounds in preparation for single range on Bound<T> - #27736
Closed
wlmyng wants to merge 6 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
wlmyng
deployed
to
sui-typescript-aws-kms-test-env
August 18, 2026 01:02 — with 
GitHub Actions
Active
GitHub Actions
Active
wlmyng
force-pushed
the
wlmyng/ledger-history-cursor-application
branch
from
August 18, 2026 01:11
bea73fa to
e35b0ab
Compare
wlmyng
deployed
to
sui-typescript-aws-kms-test-env
August 18, 2026 01:11 — with
GitHub Actions
Active
GitHub Actions
Active
wlmyng
changed the title
Resolved*Range.apply_cursor_bounds
wlmyng
force-pushed
the
wlmyng/ledger-history-cursor-application
branch
from
August 18, 2026 18:35
e35b0ab to
a91726f
Compare
wlmyng
deployed
to
sui-typescript-aws-kms-test-env
August 18, 2026 18:35 — with
GitHub Actions
Active
GitHub Actions
Active
… one wire-visible change: if after-Item is u64max, it previously early returned, now it just follows the ordinary emptying path. This means if both cursors are present, the before-arm now participates instead of being short-circuited, and attribution goes to the min position
wlmyng
force-pushed
the
wlmyng/ledger-history-cursor-application
branch
from
August 18, 2026 19:39
a91726f to
9502f5b
Compare
wlmyng
deployed
to
sui-typescript-aws-kms-test-env
August 18, 2026 19:39 — with
GitHub Actions
Active
GitHub Actions
Active
wlmyng
changed the title
Resolved*Range.apply_cursor_boundsResolved*Range.apply_cursor_bounds in preparation for single range on Bound<T>
8 tasks
Contributor
Author
|
Superseded by a re-cut of this stack with cleaner PR boundaries (renames → behavior-preserving consolidation with characterization pins → wire-semantics alignment → unification → symbolic resume): #27751 → #27752 → #27753 → #27754 → #27755. Content is carried over commit-for-commit; the old branch stays as reference. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Reorganize the logic around applying cursor bounds, in preparation for a single range generic on the scan coordinates
the refactor reveals the following asymmetries:
Range<u64> vsBound`IntraTxis symbolic (Itemmaps toExcluded,Boundarymaps toIncluded)Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.