Skip to content

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

Open
lance-gatefixer[bot] wants to merge 127 commits into
mainfrom
gatekeeper/fix-8851-1
Open

docs: correct stable row ID migration and storage#8852
lance-gatefixer[bot] wants to merge 127 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34463906402 and reports 0/3 PMC approvals on this commit; evaluator job 102827874280 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and remote identity, inspected the live checks and evaluator logs, validated protos/table.proto, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34467763167 and reports 0/3 PMC approvals on this commit; evaluator job 102840241150 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and remote identity, inspected the live checks and evaluator logs, validated protos/table.proto, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34469167160 and reports 0/3 PMC approvals on this commit; evaluator job 102844757660 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and remote identity, inspected the live checks and evaluator logs, validated protos/table.proto, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34470899534 and reports 0/3 PMC approvals on this commit; evaluator job 102850302551 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34473037906 and reports 0/3 PMC approvals on this commit; evaluator job 102857165918 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34474527762 and reports 0/3 PMC approvals on this commit; evaluator job 102862011900 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34474527762 and reports 0/3 PMC approvals on this commit; evaluator job 102862011900 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34477438048 and reports 0/3 PMC approvals on this commit; evaluator job 102871551443 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34480157086 and reports 0/3 PMC approvals on this commit; evaluator job 102880647216 completed successfully, and every current-head Rust, Python, build, and lint Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34482196980 and reports 0/3 PMC approvals on this commit; evaluator job 102887499507 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live checks and evaluator logs, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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

lance-gatefixer Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

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

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34484676611 and reports 0/3 PMC approvals on this commit; evaluator job 102895834892 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live issue, reviews, inline threads, PR conversation, checks, and evaluator log, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34486389402 and reports 0/3 PMC approvals on this commit; evaluator job 102901641757 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live issue, reviews, inline threads, PR conversation, checks, and evaluator log, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34488705298 and reports 0/3 PMC approvals on this commit; evaluator job 102909514784 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live issue, reviews, inline threads, complete PR conversation, checks, and evaluator log, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34489807437 and reports 0/3 PMC approvals on this commit; evaluator job 102913288473 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live issue, reviews, inline threads, complete PR conversation, checks, and evaluator log, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34492986071 and reports 0/3 PMC approvals on this commit; evaluator job 102924196200 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live issue, reviews, inline threads, complete PR conversation, checks, and evaluator log, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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: remote head 57690d86933d19ac989c481ca4cabbc05e7e3732 cannot satisfy format-spec-vote until the required PMC approval process completes.

The verified remote head contains current main tip 8a145b348611360f587b08c689b8cd141aefc300. The only failing current-head status is format-spec-vote, which targets Actions run 34495343986 and reports 0/3 PMC approvals on this commit; evaluator job 102932245912 completed successfully, and every executable current-head Check passes. I fetched both branches, verified ancestry and exact Ready PR identity, inspected the live issue, reviews, inline threads, complete PR conversation, checks, and evaluator log, compiled protos/table.proto, built the documentation, ran git diff --check, and verified the normal same-branch push was already up to date; 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 format-spec-vote check cannot pass because commit 57690d8 has 0 of the required 3 PMC approvals.

Evidence: the remote repair head contains the current main tip 8a145b3; Actions run 34496362200, evaluator job 102935719123, completed successfully and reported 0/3 PMC approvals on this commit.

Attempted: regenerated the protobuf descriptors, ran git diff --check, and built the documentation with uv run mkdocs build; validation passed (with existing documentation warnings), and a normal push confirmed the remote branch is up to date.

Smallest action: obtain three PMC approvals on this commit. As a practical alternative, a maintainer can apply format-waived.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 57690d8 cannot satisfy format-spec-vote because current run 34499517372 reports 0/3 required PMC approvals.

The remote repair head contains current main tip 8a145b3. Evaluator job 102946456240 and every step completed successfully, confirming this is the approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

lance-gatekeeper[bot]

This comment was marked as outdated.

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 279cc4e cannot satisfy format-spec-vote because current run 34502724332 reports 0/3 required PMC approvals.

The remote repair head contains current main tip d7b031f. Evaluator job 102957202085 and every step completed successfully, confirming this is the approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 279cc4e cannot satisfy format-spec-vote because current run 34505723070 reports 0/3 required PMC approvals.

The remote repair head contains current main tip d7b031f. Evaluator job 102967307902 and every step completed successfully, confirming this is the approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

@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 updates Torch and related dependency entries in python/uv.lock; 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: Remote head 3d9497d350012acaeec06a883562985d70696250 cannot satisfy format-spec-vote because Actions run 34508688681 reports 0/3 required PMC approvals.

The remote repair head contains current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. Evaluator job 102977104107 and every step completed successfully, confirming this is the required approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 3d9497d350012acaeec06a883562985d70696250 cannot satisfy format-spec-vote because Actions run 34511884158 reports 0/3 required PMC approvals.

The remote repair head contains current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. Evaluator job 102987757776 and every step completed successfully, confirming this is the required approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 3d9497d350012acaeec06a883562985d70696250 cannot satisfy format-spec-vote because Actions run 34511884158 reports 0/3 required PMC approvals.

The remote repair head contains current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. Evaluator job 102987757776 and every step completed successfully, confirming this is the required approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 3d9497d350012acaeec06a883562985d70696250 cannot satisfy format-spec-vote because Actions run 34515411612 reports 0/3 required PMC approvals.

The remote repair head contains current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. Evaluator job 102999461430 and every step completed successfully, confirming this is the required approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, ran git diff --check, built the documentation successfully with existing warnings, and confirmed a normal same-branch push was already up to date.

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

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 3d9497d350012acaeec06a883562985d70696250 cannot satisfy format-spec-vote because the current evaluator reports 0/3 required PMC approvals.

The remote repair head contains current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. The live status targets Actions run 34517912508; evaluator job 103007891056 and every step completed successfully, establishing that this is the required approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, built the documentation successfully with existing warnings, ran git diff --check, and confirmed a normal same-branch push was already up to date.

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

@lance-gatefixer

Copy link
Copy Markdown
Contributor Author

Blocked: Remote head 3d9497d350012acaeec06a883562985d70696250 cannot satisfy format-spec-vote because the current evaluator reports 0/3 required PMC approvals.

The remote repair head contains current main tip 31d78d1707c1d2cff01ed1ab111fe9cfc58d50d8. The live status targets Actions run 34519540493; evaluator job 103013314323 and every step completed successfully, establishing that this is the required approval gate rather than an attributable code failure.

Attempted: fetched and verified both refs and the exact Ready PR identity, inspected the current status and evaluator log, compiled protos/table.proto, built the documentation successfully with existing warnings, ran git diff --check, and confirmed a normal same-branch push was already up to date.

The smallest next action is for three eligible PMC members to provide binding approvals on this commit. Alternatively, a PMC member may apply format-waived if the 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

0 participants