Repository navigation
rpc: serve ListObjectVersions from the fullnode within its retention window - #28645
Draft
nickvikeras wants to merge 1 commit into
Draft
nickvikeras wants to merge 1 commit into
nickvikeras wants to merge 1 commit into
Conversation
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 11, 2026 17:15
c90a27d to
0619a00
Compare
1 of 8 tasks
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 11, 2026 17:30
21ae310 to
de1a529
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 11, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 18:21
0619a00 to
7cd7deb
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
2 times, most recently
from
November 12, 2026 18:53
155145a to
78d06ac
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 18:59
7cd7deb to
8fc0f03
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 19:06
78d06ac to
209f2d2
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 20:20
8fc0f03 to
0a1a459
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 20:33
209f2d2 to
d657237
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 21:09
d657237 to
ed7b7fe
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 21:17
0a1a459 to
6a71e2f
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 21:34
ed7b7fe to
2e8b0d6
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 22:11
2e8b0d6 to
2c1824a
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 22:30
6a71e2f to
82c8788
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 22:46
2c1824a to
cabbda9
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 23:02
82c8788 to
a8fa55b
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 12, 2026 23:12
cabbda9 to
6d49ee5
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 12, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 12, 2026 23:54
a8fa55b to
be6c21d
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 13, 2026 00:18
6d49ee5 to
734593f
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
2 times, most recently
from
November 13, 2026 01:02
3fdf275 to
6dc4790
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 13, 2026 01:10
734593f to
b69b163
Compare
nickvikeras
added a commit
that referenced
this pull request
Nov 13, 2026
# Conflicts: # Cargo.lock # Cargo.toml # crates/sui-fork/src/tests/store_execution.rs # crates/sui-indexer-alt-e2e-tests/tests/kv_rpc_tests.rs # crates/sui-kvstore/src/bigtable/client/mod.rs # crates/sui-kvstore/src/bigtable/mock_server.rs # crates/sui-kvstore/src/tables/objects.rs # crates/sui-rpc-api/src/reader.rs # crates/sui-types/src/storage/read_store.rs
1 of 8 tasks
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 13, 2026 04:15
b69b163 to
cbbf11a
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
2 times, most recently
from
November 13, 2026 04:53
b24c252 to
9c078b4
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 13, 2026 04:53
cbbf11a to
698c3ef
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 13, 2026 05:02
9c078b4 to
9a6e75f
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
2 times, most recently
from
November 13, 2026 11:11
44cdb68 to
ba3452c
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 13, 2026 11:11
9a6e75f to
9721a19
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 14, 2026 01:04
ba3452c to
f34e4e1
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
2 times, most recently
from
November 14, 2026 06:25
1912f75 to
ecb0307
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 14, 2026 06:25
f34e4e1 to
1b966b0
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 14, 2026 18:50
ecb0307 to
d4a6aaf
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
2 times, most recently
from
November 15, 2026 02:09
b530dec to
b0e9aa5
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 15, 2026 02:09
d4a6aaf to
509c3be
Compare
…window Fullnodes keep every object version within their retention window, so they serve ListObjectVersions for the objects whose history they retain instead of answering UNIMPLEMENTED. The handler reuses #28632's ObjectVersionsQuery, plan and frames, and reads items in chunks of blocking reads of the perpetual objects table, through a new ObjectCacheRead::object_versions_iter. Below the retention floor F, the checkpoint at whose end object state is intact (as for at_checkpoint reads), an object's oldest retained version is its version at the end of F, or, for an object with no version there, its first item after F unless that item is a creation under a new ID. A range starting below it fails with OUT_OF_RANGE / BELOW_EARLIEST_AVAILABLE, with lowestAvailableCheckpoint and a new lowestAvailableVersion; an object with nothing retained fails with lowestAvailableCheckpoint only. Items are placed through the rpc indexes, which prune in the same write that raises F, and the floor is read again after each chunk, so a prune during a listing fails it instead of cutting it short. A removal's transaction is found by walking the object's transactions in the bitmap's affected-object dimension back from its next item, and only when removal_read_mask selects transaction. Such a listing's floor is the higher of F and the checkpoint before the lowest one with removal transactions (lowest_available_checkpoint - 1), and a removal above it whose transaction cannot be found fails the listing with INTERNAL. Adds RpcIndexes::ledger_tx_seq_by_digest, and for the tests AuthorityStore::prune_objects_and_rpc_store_for_testing and two fail points, compiled only under msim or the fail_points feature.
nickvikeras
force-pushed
the
nickv/list-object-versions
branch
from
November 15, 2026 19:59
509c3be to
4806862
Compare
nickvikeras
force-pushed
the
nickv/list-object-versions-fullnode
branch
from
November 15, 2026 19:59
b0e9aa5 to
0ee2270
Compare
This branch has not been deployed
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
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
Fullnodes keep every object version within their retention window, so they can serve
ListObjectVersionsthemselves for objects whose history is retained, instead of answeringUNIMPLEMENTEDand leaving every listing to archival kv-rpc.Mini design doc
Design. The fullnode handler reuses the shared request handling from #28632:
ObjectVersionsQueryparses the request,bounding_checkpointandplanfold the version range, cursors andat_checkpointinto one inclusive range and choose theQueryEndreason, andframesemits the frames fromObjectVersionItems, each removal with the fieldsremoval_read_maskselects. The handler adds the reads, the retention floor and, when the mask selects it, each removal's transaction. Before anything is listed, a blocking task reads the object's version at the bounding checkpoint and the retention floor. The items are then read in chunks of blocking RocksDB reads onChunkedScan(up tochunk-max, default 32, per chunk), so a slow client holds neither an iterator nor a blocking thread. A newRpcIndexes::object_versions_iter, like the other*_iterreads, iterates one range of an object's versions, live objects and the deletion and wrap tombstones (ObjectOrTombstone); each chunk opens it for the versions it has left and takes up tochunk-maxitems. Each tombstone is listed as a removal (DELETEDorWRAPPED).Floor rule. The floor checkpoint F is the lowest checkpoint whose object state is intact: the floor
GetObject'sat_checkpointreads already use (one below the higher of the lowest checkpoint with object data and the lowest with index history). Pruning removes the versions an object replaced, and the tombstones written, at or before the end of F, and keeps its live version at the end of F. Removals written after F are retained items. When anything below F is gone:The object's oldest retained version is its version at the end of F. An object with no version there was created after F, or removed at or before F and then unwrapped, or created again under the same ID, after F; pruning drops a removed object's index rows. Its first item after F decides which. Items are placed through the rpc indexes alone: a live version by its transaction's sequence number (
tx_seq_by_digest) and that transaction's checkpoint (tx_metadata_by_seq), a deletion by its removal transaction (see below). The indexes prune both in the same write that raises the floor, so an item they can no longer place was written at or before F and is skipped. A live version whose transaction created the object under a new ID keeps the whole history.object::newderives every ID it creates from the creating transaction's digest and a count (ObjectID::derive_id), so a new ID is one that matches some count the transaction could reach. An ID that matches no count costs all 32,768 counts the system-transaction limit allows, about 5.6 ms in a release build. So when the creating transaction's effects are kept, they settle the common cases first:Field<derived_object::Claimed, ClaimedStatus>named after it to the parent in the same transaction.A dynamic field is ruled out by its type before any of that, and a new ID matches within the first few counts. Only effects that are pruned, or a derived object whose claim marker came from an earlier transaction, run the whole loop. Anything else makes that item the oldest retained one:
sui::derived_object(released and claimed again). Their IDs are hashes of a parent and a key, which never match a derived ID. A first creation looks the same as a re-creation, so every such object created after F is listed from its first version;If the listing's range starts below the oldest retained version, an ascending listing fails before listing anything, with
start_versionor anaftercursor or neither.In the same case, a descending listing lists every retained item in range, then fails instead of sending a
QueryEnd, unless it reachesITEM_LIMITfirst.Both fail with
OUT_OF_RANGE/BELOW_EARLIEST_AVAILABLE,lowestAvailableCheckpoint= F and the newlowestAvailableVersion= the oldest retained version, so a client can retry withstart_versionset to it. A range starting at or above that version is served normally.An object with no retained item at all, live or removal (deleted or wrapped at or before F, or never created; the node cannot tell which), fails with
BELOW_EARLIEST_AVAILABLEand onlylowestAvailableCheckpoint. That check runs before any cursor is compared with the tip. A node that has pruned no objects knows such an object never existed, and lists nothing, even for a listing whose transaction floor is set.at_checkpointbelow F fails asGetObject's does. A node running the objects compactor answersUNIMPLEMENTED/NOT_SERVED_HERE(causeno_object_history), one without rpc indexesUNIMPLEMENTED/NOT_SERVED_HERE(no_rpc_indexes), and one still backfilling index history after a restoreUNAVAILABLE/NOT_READY(restore_backfill), through the checksat_checkpointreads use.Removal transactions. Object IDs can be reused: dynamic fields and derived objects can be deleted and created again under the same ID, at a higher version. Nothing changes a deleted object until a transaction creates it again, nor a wrapped one until a transaction unwraps or deletes it. That transaction writes the object's next item, unless it creates the object straight into a wrapper (a derived object claimed into a wrapper, with effects
(NotExist, NotExist, Created)), which changes the object without writing an item of it. So the handler walks the object's transactions in the transaction bitmap's affected-object dimension back from the transaction of its next item, or, with no next item, from the end of the indexed transactions:RpcIndexes::ledger_tx_seq_by_digest(the rpc-store'stx_seq_by_digest); a next tombstone through its own removal.The next item is read from storage, not from the page, so the answer doesn't depend on paging or chunking. Every lookup in a listing is bounded by the highest indexed checkpoint as of planning, so it reads only what the indexes have committed.
Decisions.
object_version_by_checkpoint. This ties the floor to the checkpoint the other at-checkpoint reads use. For objects with no row there, Nick chose to tell a creation from an unwrap by looking at the first version after F, over having the pruner keep each removed object's tombstone row forever. The creation check derives IDs from the transaction digest, so it still works when the creating effects are pruned. The cost is that objects whose IDs can be reused are treated as truncated.num_epochs_to_retain=u64::MAX) runs above F.removal_read_maskselectstransaction; with the defaultversion,kindnothing looks for it. A listing that asks for it has the higher of two floors: the object floor, and the checkpoint before the lowest one with removal transactions (GetServiceInfo'slowest_available_checkpoint, minus one). Both floors name the checkpoint at whose end the listing's history starts: the listing starts from each object's state at the end of it, and everything it lists after that was written in later checkpoints, which have their removal transactions. That is the same convention as the object floor (AtCheckpointLowerBound::pruned_floor, the checkpoint before its lowest available one), andlowestAvailableCheckpointin the refusal names it. Taking the lowest checkpoint with removal transactions itself would refuse that checkpoint's removals for no reason. The two floors differ only on nodes that keep every object version and prune checkpoints. There the version index still holds an object's removal at or before the higher floor, whose transaction is pruned, so such an object has no version at that floor: its oldest retained version is its first item after the removal, every one of which was written after the floor, or, with none, it keeps nothing. Above the floor, a removal whose transaction cannot be found fails the listing withINTERNAL, after the floor is read again, so pruning that raced the read gets the floor error instead (but see the known gap below). A missing summary of the indexed tip checkpoint, which bounds the walk, isINTERNALtoo.killswitch_tombstone_pruningkeeps tombstones indefinitely, so the search for the oldest retained version can meet tombstones written at or before F. That search runs only for an object with no version at the end of F.WRAPPEDtombstone it meets is skipped: a wrap after F would follow a live version written after F, which comes first.DELETEDtombstone is placed by its removal transaction's checkpoint. A deletion the indexes can no longer place is at or before F and skipped. A retained deletion with pruned effects still sets the floor, through its unconfirmed removal. If that unconfirmed transaction is a re-claim into a wrapper after F while the deletion itself was at or before F, the listing starts at the stored deletion, and every item after it was written after F. A deletion at or before F followed by a re-creation of the ID after F is skipped, and the floor falls on the re-creation.BELOW_EARLIEST_AVAILABLEand onlylowestAvailableCheckpoint, as for an object with nothing retained, rather than ending as if it had listed everything. Each floor read is repeated until the floor is the same before and after it, so the lookup never sees a half-applied prune. A descending listing's final floor error is built from the last chunk's floor read, so it names the currentlowestAvailableCheckpoint.objectstable. The embedded rpc-store does not hold object bytes, so the read goes throughAuthorityState's object cache like the other object reads, as a newObjectCacheRead::object_versions_iter. The writeback cache holds no ranges, so that method reads the perpetual table alone and sees only committed versions. That is enough because the indexer receives a checkpoint only after its objects are committed. The executor broadcasts a checkpoint after committing it, andPerpetualStoreIngestionClientnow refuses checkpoints above the highest executed one. That client could previously index a checkpoint whose data was readable only from the cache.RpcIndexes, notRpcStateReader. The listing needs the indexes for its checkpoint bound anyway. Backends without indexes (simulacrum,RestReadStore, the transactional test runner) answerUNIMPLEMENTED/NOT_SERVED_HERE(no_rpc_indexes) before any version read, and do not need an implementation.lamport_version, which V1 effects recompute from the modified objects alone, below the tombstone the object store holds. The listing resolves an indexed version with no row to the tombstone just above it, asGetObjectdoes, so such a removal is still listed when it is the object's last item.AuthorityStore::prune_objects_and_rpc_store_for_testingprunes the objects and the rpc indexes through a checkpoint as the background pruner does, keeping tombstones or not, so tests control where F lands. Two fail points,prune-objects-before-perpetual-commitandlist-object-versions-after-plan, compile to nothing outside the simulator; they pause a prune between its two commits and a listing between its plan and its first chunk.ChunkedScangains a terminal type parameter, because a version listing has no ledger watermark to carry. The existing List APIs keepScanTerminalas the default.Parity with kv-rpc. Both backends parse requests, plan ranges, pick
QueryEndreasons, mint cursors (ObjectVersionCursor) and emit frames with the samesui-rpc-apicode. They give the same answer for every object whose history the fullnode retains. A cursor from either backend decodes on the other. The sharedplanhandles a cursor above the object's version at the indexed tip as the otherList*RPCs do: a descending listing fails withABOVE_LATEST_AVAILABLE, and an ascending one is served from this server's view and, unlessend_versionorbeforeends it first, ends withLEDGER_TIP. On the fullnode the tip is its highest indexed checkpoint. Only the fullnode applies the floor rules, which follow #43's contract: history is kept from each object's state at the end oflowestAvailableCheckpoint, and the server may report a higher oldest retained version than an object strictly needs.Impact and rollout. Fullnodes start answering
ListObjectVersions. New configledger-history.list-object-versions(timeout-ms,default-limit-items50,max-limit-items1000,chunk-max32). Its chunks are timed in the sharedlist_chunk_secondshistogram, withmethod="list_object_versions". No protocol change.Test coverage. Fullnode simtests read two versions per chunk, so every listing crosses chunk boundaries. They cover:
WRAPPEDandDELETEDremovals with their transactions, listed in both orders and paged by cursor with every removal's transaction intact on every page size. Also the wrapper, deleted by the unwrap;at_checkpointat every checkpoint of the lifecycle;CURSOR_BOUND,CHECKPOINT_BOUNDandLEDGER_TIPends, an ascendingafterpast the tip ending withLEDGER_TIP, and a descendingbeforepast the tip failing withoutat_checkpointand served with it;end_versionat the oldest retained version;start_versionexactly at the oldest retained version, andITEM_LIMITat the floor;at_checkpointat and below the floor;BELOW_EARLIEST_AVAILABLE; another raises the oldest retained version above where the listing starts and fails it with the new version.Unit tests cover the listing floor with and without removal transactions, the creation check's ID derivation and claim marker, the resolution of a removal indexed below its tombstone, the
sui-rpc-storerange read with tombstones, the ingestion client's executed-tip gate, and the bitmap rule the removal walk relies on: a transaction that only references a deleted shared object adds noAffectedObjectentry for it.Not covered by a test:
INTERNAL: no real store reaches it outside the race below. A mutation that drops the transaction floor reaches it, andlist_object_versions_deleted_with_pruned_effectsfails on that mutation;Known gap:
AuthorityStorePruner::prune_checkpointsdeletes the effects (perpetual_batch) before it raises the checkpoint floor (checkpoints_batch,HighestPruned). A listing that asks for transactions and reads a removal between those two writes finds its effects gone while the floor recheck still sees the old floor, and fails withINTERNALinstead of the floor error. Writing the checkpoint batch first would close the window, but a crash between the two writes would then leave that checkpoint's effects unpruned for good. The pruner's write order is a follow-up.Test plan
New simtests:
list_object_versions_lifecyclelist_object_versions_below_oldest_retained_versionlist_object_versions_created_after_the_floorlist_object_versions_reused_idlist_object_versions_claimed_again_after_the_floorlist_object_versions_claimed_again_after_background_pruning(simulator only)list_object_versions_unwrapped_after_the_floorlist_object_versions_reclaimed_into_a_wrapperlist_object_versions_reclaimed_into_a_wrapper_after_the_floorlist_object_versions_deleted_with_pruned_effectslist_object_versions_leftovers_while_pruning(simulator only)list_object_versions_pruned_while_listing(simulator only)list_object_versions_floor_rises_while_listing(simulator only)New unit tests:
created_under_new_id_tells_reusable_ids_apartremoval_indexed_below_its_tombstone_resolves_to_itobject_versions_iter_lists_tombstones_within_boundscheckpoint_above_highest_executed_is_not_foundtransaction_visitor_skips_consensus_objects_whose_stream_endedlisting_floor_is_the_checkpoint_before_transaction_data_when_higherRelease notes
LedgerService.ListObjectVersionsfor objects within their retention window, including the versions at which an object was deleted or wrapped, and, whenremoval_read_maskselectstransaction, the transaction that removed it. A listing that would start or end inside pruned history fails withOUT_OF_RANGE/BELOW_EARLIEST_AVAILABLE, naming the oldest retained version inlowestAvailableVersion, or, for an object the node retains nothing of, onlylowestAvailableCheckpoint. On a node that prunes checkpoints sooner than objects, a listing that asks for removal transactions has the higher of the two floors.