Skip to content

docs: correct stable row ID migration and storage - #8852

Merged
Xuanwo merged 130 commits into
mainfrom
gatekeeper/fix-8851-1
Sep 11, 2026
Merged

docs: correct stable row ID migration and storage#8852
Xuanwo merged 130 commits into
mainfrom
gatekeeper/fix-8851-1

Conversation

@lance-gatefixer

Copy link
Copy Markdown
Contributor

Summary

  • document how existing datasets migrate to stable row IDs and the index/concurrency constraints
  • clarify that current writers always emit row ID and version sequences inline
  • mark external version-sequence fields as unsupported and reserved while retaining the supported external row-ID read contract

Root cause

The format documentation and protobuf comments still described pre-implementation plans: they said existing datasets could not migrate and presented a 200 KB inline/external threshold as active writer behavior. Migration has since shipped, but writers still emit every sequence inline and readers cannot load external version sequences.

Validation

  • protoc --proto_path=../protos --descriptor_set_out=/dev/null ../protos/table.proto
  • uv run mkdocs build (completed with pre-existing missing-link warnings outside this change)
  • git diff --check

Fixes #8851

@github-actions github-actions Bot added A-format On-disk format: protos and format spec docs format-change A change to the format spec, which requires a vote. Remove if minor (e.g. fixing typo). documentation Improvements or additions to documentation labels Aug 28, 2026
@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Important

Format specification vote

This PR modifies the Lance format specification, so it requires 3 binding +1 votes from PMC members (excluding the proposer) and a minimum 72-hour voting period, weekends excluded, before it can merge. Vote by approving this PR (+1) or requesting changes (−1, a veto). See the voting process.

Status: ❌ Blocked — 0 of 3 required approvals

Approvals (this commit) none (0/3)
Vetoes none
Voting period elapsed — ended Wed 2026-09-02 19:20 UTC (12:20 PDT)

Updated automatically by the format-spec vote gate, which re-checks every 15 minutes — just voted? Re-check now (press Run workflow; leave the input blank to re-check every open format PR). A PMC member may apply the format-waived label to waive the vote for a trivial edit (typo, wording, formatting).

lance-gatekeeper[bot]

This comment was marked as outdated.

@lance-gatekeeper lance-gatekeeper Bot added the K-changes Latest Gatekeeper recommendation requests changes. label Aug 28, 2026
@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot pass format-spec-vote until the required PMC approval process is satisfied.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1; the live format-spec-vote status reports 0/3 PMC approvals on this commit, while Actions run 33204888739 and its evaluator job completed successfully. I fetched both branches, verified ancestry, inspected the current-head status and logs, and found no terminal build or test failure or attributable code defect to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatekeeper lance-gatekeeper Bot removed the K-changes Latest Gatekeeper recommendation requests changes. label Aug 28, 2026
lance-gatekeeper[bot]

This comment was marked as outdated.

@lance-gatekeeper lance-gatekeeper Bot added the K-approved Latest Gatekeeper recommendation permits acceptance. label Aug 28, 2026
@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot pass format-spec-vote until the required PMC approval process is satisfied.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1; the live format-spec-vote status reports 0/3 PMC approvals on this commit, while current-head Actions run 33205470285 and its evaluator job completed successfully. I fetched both branches, verified ancestry, inspected all current-head checks and the evaluator logs, and found no terminal build or test failure or attributable code defect to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head is held by an unrelated Windows runner failure and the required format-spec approval gate.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1. Python windows job 98963312295 failed only test_torch_index_with_nans[Legacy] because PyTorch Inductor received PermissionError reopening a generated runner-temp file; the same test passed on Windows for the exact base in job 98918373866, and this branch changes only Markdown and protobuf comments. Separately, format-spec-vote reports 0/3 PMC approvals on this commit. I fetched both branches, verified ancestry, compared the current-head and exact-base logs, and found no attributable code defect to repair. The smallest next actions are to rerun the failed Windows job on a clean hosted runner and obtain the required three binding +1 PMC approvals after the voting period; practical alternatives are rerunning the full Python workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head remains held by an unrelated Windows hosted-runner failure and the required format-spec approval gate.

Remote head 6682e7ddccc27d8a3fa28c9cdd297dfd906496de contains the current main tip 5b14b344e8c9757036cc7cf0b2e134ee233560b1. Python windows job 98963312295 failed only test_torch_index_with_nans[Legacy] because PyTorch Inductor received PermissionError reopening a generated runner-temp file; exact-base Windows job 98918373866 passed that test and all 1,364 tests, while this branch changes only Markdown and protobuf comments. Separately, format-spec-vote reports 0/3 PMC approvals on this commit, and evaluator run 33209947118 completed successfully. I fetched both branches, verified ancestry, compared the current-head and exact-base logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next actions are to rerun the failed Windows job on a clean hosted runner and obtain three binding +1 PMC approvals after the voting period; practical alternatives are rerunning the full Python workflow and, if this documentation correction qualifies as trivial, having a PMC member apply format-waived.

@lance-gatekeeper lance-gatekeeper Bot removed the K-approved Latest Gatekeeper recommendation permits acceptance. label Aug 28, 2026
lance-gatekeeper[bot]

This comment was marked as outdated.

@lance-gatekeeper lance-gatekeeper Bot added the K-approved Latest Gatekeeper recommendation permits acceptance. label Aug 28, 2026
@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33216656108 and reports 0/3 PMC approvals on this commit; its evaluator job 99001687932 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33217104161 and reports 0/3 PMC approvals on this commit; its evaluator job 99003082863 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33218990261 and reports 0/3 PMC approvals on this commit; its evaluator job 99008845859 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33219934264 and reports 0/3 PMC approvals on this commit; its evaluator job 99011652281 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5 contains the current main tip 085354e. The live format-spec-vote status targets Actions run 33220685156 and reports 0/3 PMC approvals on this commit; its evaluator job 99013887195 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33221480344 and reports 0/3 PMC approvals on this commit; its evaluator job 99016231702 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 01197a5e6e91acb18b0bf5bfd8f7d33538c44a55 contains the current main tip 085354e6ac9f6178aa15fcb4bb1ab410c82bd203. The live format-spec-vote status targets Actions run 33222441276 and reports 0/3 PMC approvals on this commit; its evaluator job 99019148730 completed successfully, and all 32 current-head CheckRuns pass. I fetched both branches, verified ancestry and remote identity, inspected the current status and evaluator logs, and ran git diff --check; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals after the required voting period; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatekeeper lance-gatekeeper Bot removed the K-approved Latest Gatekeeper recommendation permits acceptance. label Aug 29, 2026
lance-gatekeeper[bot]

This comment was marked as outdated.

@lance-gatekeeper lance-gatekeeper Bot added the K-approved Latest Gatekeeper recommendation permits acceptance. label Aug 29, 2026
@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103125596250, completed successfully and explicitly recorded that vote result; all current-head CheckRuns succeeded. I revalidated the protobuf schema, built the format documentation, checked the branch diff for whitespace errors, and confirmed a normal push is already up to date, so there is no evidenced code or infrastructure failure to repair.

To unblock the PR, three PMC members must approve this exact commit under the format-spec vote process, after which the evaluator can update the status. As a practical alternative, maintainers can revise or supersede the format-spec proposal through the normal governance process and provide the resulting concrete direction for the FixAgent.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103128971839, completed successfully and explicitly recorded that vote result; all current-head CheckRuns succeeded. I revalidated the protobuf schema, built the format documentation, checked the branch diff for whitespace errors, and confirmed a normal push is already up to date, so there is no evidenced code or infrastructure failure to repair.

To unblock the PR, three PMC members must approve this exact commit under the format-spec vote process, after which the evaluator can update the status. As a practical alternative, maintainers can revise or supersede the format-spec proposal through the normal governance process and provide the resulting concrete direction for the FixAgent.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103131430721, completed successfully and explicitly recorded that vote result; all current-head CheckRuns succeeded. I revalidated the protobuf schema, built the format documentation, checked the branch diff for whitespace errors, and confirmed a normal push is already up to date, so there is no evidenced code or infrastructure failure to repair.

To unblock the PR, three PMC members must approve this exact commit under the format-spec vote process, after which the evaluator can update the status. As a practical alternative, maintainers can revise or supersede the format-spec proposal through the normal governance process and provide the resulting concrete direction for the FixAgent.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103136123028, completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. This establishes a required approval gate, not an attributable code or infrastructure failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the live issue, reviews, inline comments, PR conversation, current status, CheckRuns, and evaluator log, compiled protos/table.proto, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and confirmed a normal same-branch push was already up to date. No attributable repository failure remains to repair.

The smallest next action is for three eligible PMC members to provide binding approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103140002418, completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. This establishes a required approval gate, not an attributable code or infrastructure failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the live issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and confirmed a normal same-branch push was already up to date. No attributable repository failure remains to repair.

The smallest next action is for three eligible PMC members to provide binding approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103142650910, completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. This establishes a required approval gate, not an attributable code or infrastructure failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the live issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and confirmed a normal same-branch push was already up to date. No attributable repository failure remains to repair.

The smallest next action is for three eligible PMC members to provide binding approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The latest format vote evaluator run, including job 103147275951, completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. This establishes a required approval gate, not an attributable code or infrastructure failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the live issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and confirmed a normal same-branch push was already up to date. No attributable repository failure remains to repair.

The smallest next action is for three eligible PMC members to provide binding approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 3d9497d350012acaeec06a883562985d70696250 contains the current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. The live format-spec-vote status targets Actions run 34563515958 and reports PR #8852: 0/3 PMC approvals on this commit; evaluator job 103150875409 completed successfully, and all 34 current-head CheckRuns pass. I fetched both branches, verified ancestry and PR identity, inspected the current status and evaluator log, ran the protobuf descriptor check and MkDocs build, checked the diff, and pushed normally; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 3d9497d350012acaeec06a883562985d70696250 contains the current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. The live format-spec-vote status targets Actions run 34564409266 and reports PR #8852: 0/3 PMC approvals on this commit; evaluator job 103153460481 completed successfully, and all 34 current-head CheckRuns pass. I fetched both branches, verified ancestry and Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, ran the protobuf descriptor check and MkDocs build, checked the diff, and pushed normally; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 3d9497d350012acaeec06a883562985d70696250 contains the current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. The live format-spec-vote status targets Actions run 34566370622 and reports PR #8852: 0/3 PMC approvals on this commit; evaluator job 103159219920 completed successfully, and all 34 current-head CheckRuns pass. I fetched both branches, verified ancestry and Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, ran the protobuf descriptor check and MkDocs build, checked the diff, and pushed normally; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: the current head cannot satisfy format-spec-vote until the required PMC approval process completes.

Remote head 3d9497d350012acaeec06a883562985d70696250 contains the current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. The live format-spec-vote status targets Actions run 34567213320 and reports PR #8852: 0/3 PMC approvals on this commit; evaluator job 103161685841 completed successfully, and all 34 current-head CheckRuns pass. I fetched both branches, verified ancestry and Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, ran the protobuf descriptor check and MkDocs build, checked the diff, and pushed normally; no attributable code defect remains to repair. The smallest next action is for three eligible PMC members to provide binding +1 approvals; alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The live status targets Actions run 34568352363; evaluator job 103164986065 completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. I fetched both refs, verified ancestry and the exact Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and pushed normally; the branch is up to date and no attributable repository failure remains.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The live status targets Actions run 34570686569; evaluator job 103171923865 completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. I fetched both refs, verified ancestry and the exact Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and pushed normally; the branch is up to date and no attributable repository failure remains.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The live status targets Actions run 34572871780; evaluator job 103178627331 completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. I fetched both refs, verified ancestry and the exact Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and pushed normally; the branch is up to date and no attributable repository failure remains.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d350012acaeec06a883562985d70696250 reports 0/3 PMC approvals on this commit.

The current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8 is an ancestor of that remote head. The live status targets Actions run 34574320984; evaluator job 103183227313 completed successfully and explicitly logged PR #8852: 0/3 PMC approvals on this commit, while all 34 current-head CheckRuns succeeded. I fetched both refs, verified ancestry and the exact Ready PR identity, inspected the issue, reviews, inline comments, full PR conversation, current status, CheckRuns, and evaluator log, compiled the protobuf schema, built the documentation successfully with existing warnings, checked the branch diff for whitespace errors, and pushed normally; the branch is up to date and no attributable repository failure remains.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit and let the vote gate re-evaluate. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d reports 0/3 PMC approvals on this commit.

Remote head 3d9497d contains the current main tip 31d78d1. All 34 current-head CheckRuns pass; the failing commit status targets Actions run 34575950370 and evaluator job 103188316327, both completed successfully, and the job log explicitly reports PR #8852: 0/3 PMC approvals on this commit. I fetched and verified base ancestry and remote identity, reviewed the live issue, PR, reviews, threads, checks, and logs, reran protobuf compilation, the documentation build, and diff validation, and pushed the assigned branch normally; no attributable repository defect remains.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this commit. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head 3d9497d reports 0/3 PMC approvals on this commit.

Remote head 3d9497d contains the current main tip 31d78d1. All 34 current-head CheckRuns pass; the failing commit status targets Actions run 34581034632 and evaluator job 103204375808, both completed successfully, and the job log explicitly reports PR #8852: 0/3 PMC approvals on this commit. I fetched and verified base ancestry and remote identity, reviewed the live issue, PR, reviews, threads, checks, and logs, reran protobuf compilation, the documentation build, and diff validation, and pushed the assigned branch normally; no attributable repository defect remains.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this commit. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

lance-gatekeeper[bot]

This comment was marked as outdated.

lance-gatekeeper[bot]

This comment was marked as outdated.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 remains blocked by an unrelated Windows hosted-runner file-access failure and the required format-spec approval gate.

Remote head f83166a contains the current main tip e89ceb3. The windows-build Check in Actions run 34584199097, job 103214490907, failed only lance::index::vector::ivf::tests::test_create_ivf_hnsw_pq because persisting a runner temporary shuffle_data.lance file returned Access is denied (os error 5); the identical test passed on exact-base Windows job 103213450797, and this branch changes only format documentation and protobuf comments. Separately, the format-spec-vote status targets run 34585889195, whose evaluator job 103219877434 completed successfully while logging PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and the exact Ready PR identity, inspected the current-head and exact-base logs and the full PR conversation, compiled the protobuf schema, built the documentation, checked the diff, and pushed the assigned branch normally; it is up to date and no attributable repository defect remains.

The smallest next actions are to rerun windows-build on a clean hosted runner and obtain three binding +1 PMC approvals on this exact commit. Practical alternatives are to rerun the full Rust workflow and, if this documentation correction qualifies as trivial, have a PMC member apply format-waived.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 remains blocked by an unrelated Windows hosted-runner file-access failure and the required format-spec approval gate.

Remote head f83166a contains the current main tip e89ceb3. The windows-build Check in Actions run 34584199097, job 103214490907, failed only lance::index::vector::ivf::tests::test_create_ivf_hnsw_pq because persisting a runner temporary shuffle_data.lance file returned Access is denied (os error 5); the identical test passed on exact-base Windows job 103213450797, and this branch changes only format documentation and protobuf comments. Separately, the format-spec-vote status targets run 34587175451, whose evaluator completed successfully while logging PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and the exact Ready PR identity, inspected the current-head and exact-base logs and the full PR conversation, compiled the protobuf schema, built the documentation, checked the diff, and pushed the assigned branch normally; it is up to date and no attributable repository defect remains.

The smallest next actions are to rerun windows-build on a clean hosted runner and obtain three binding +1 PMC approvals on this exact commit. Practical alternatives are to rerun the full Rust workflow and, if this documentation correction qualifies as trivial, have a PMC member apply format-waived.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 remains blocked by an unrelated Windows hosted-runner file-access failure and the required format-spec approval gate.

Remote head f83166a contains the current main tip e89ceb3. The windows-build Check in Actions run 34584199097, job 103214490907, failed only lance::index::vector::ivf::tests::test_create_ivf_hnsw_pq because persisting a runner temporary shuffle_data.lance file returned Access is denied (os error 5); the identical test passed on exact-base Windows job 103213450797, and this branch changes only format documentation and protobuf comments. Separately, the format-spec-vote status targets run 34589021421, whose evaluator completed successfully while logging PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and the exact Ready PR identity, inspected the current-head and exact-base logs and the full PR conversation, compiled the protobuf schema, built the documentation, checked the diff, and pushed the assigned branch normally; it is up to date and no attributable repository defect remains.

The smallest next actions are to rerun windows-build on a clean hosted runner and obtain three binding +1 PMC approvals on this exact commit. Practical alternatives are to rerun the full Rust workflow and, if this documentation correction qualifies as trivial, have a PMC member apply format-waived.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 remains blocked by an unrelated Windows hosted-runner file-access failure and the required format-spec approval gate.

Remote head f83166a contains the current main tip e89ceb3. The windows-build Check in Actions run 34584199097, job 103214490907, failed only lance::index::vector::ivf::tests::test_create_ivf_hnsw_pq because persisting a runner temporary shuffle_data.lance file returned Access is denied (os error 5); the identical test passed on exact-base Windows job 103213450797, and this branch changes only format documentation and protobuf comments. Separately, the format-spec-vote status targets run 34589767488, whose evaluator completed successfully while logging PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and the exact Ready PR identity, inspected the current-head and exact-base logs and the full PR conversation, compiled the protobuf schema, built the documentation, checked the diff, and pushed the assigned branch normally; it is up to date and no attributable repository defect remains.

The smallest next actions are to rerun windows-build on a clean hosted runner and obtain three binding +1 PMC approvals on this exact commit. Practical alternatives are to rerun the full Rust workflow and, if this documentation correction qualifies as trivial, have a PMC member apply format-waived.

@lance-gatekeeper lance-gatekeeper Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gate recommendation: approve.

The pull-request patch remains unchanged. The new base commit only changes scheduling and coverage for already-bounded blob reads; it does not alter stable-row-ID migration, index coordination, physical-row accounting, or row/version-sequence storage. The corrected migration and storage guidance remains accurate.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head d1a4c72 reports 0/3 PMC approvals on this commit.

Remote head d1a4c72 contains the current main tip 1b90368. The live PR rollup has 32 passing checks and only format-spec-vote failing; its status targets Actions run 34593624029, and evaluator job 103244286807 completed successfully while logging PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and Ready PR identity, read the live issue, PR, reviews, threads, full conversation, checks, and evaluator logs, and reran protobuf compilation, the documentation build, and diff validation. No attributable repository defect remains, so no speculative code change or push was made.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: PR #8852 cannot merge because the required format-spec-vote status on remote head d1a4c72 reports 0/3 PMC approvals on this commit.

Remote head d1a4c72 contains the current main tip 1b90368. The live PR rollup has 32 passing checks and only format-spec-vote failing; its status targets Actions run 34594414646, and evaluator job 103246737159 completed successfully while logging PR #8852: 0/3 PMC approvals on this commit.

I fetched both refs, verified base ancestry and Ready PR identity, read the live issue, PR, reviews, threads, full conversation, checks, and evaluator logs, and reran protobuf compilation, the documentation build, and diff validation. No attributable repository defect remains, so no speculative code change or push was made.

The smallest next action is for three eligible PMC members to provide binding +1 approvals on this exact commit. Alternatively, a PMC member may apply format-waived if this documentation correction qualifies as trivial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-format On-disk format: protos and format spec docs documentation Improvements or additions to documentation format-change A change to the format spec, which requires a vote. Remove if minor (e.g. fixing typo). K-approved Latest Gatekeeper recommendation permits acceptance.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: stable row id spec describes migration and inline/external storage inaccurately

1 participant