Move the client-rust pin past the merged fixes; re-state converged claims #10

Activity

1. eduralph

   added this to the Phase 0 — Land what is already in flight milestone on Jul 14, 2026
2. eduralph

   added

   blockedCannot start until a prerequisite (often an upstream merge) landsCannot start until a prerequisite (often an upstream merge) lands

   on Jul 18, 2026
3. eduralph commented on Jul 18, 2026

   

   eduralph

   on Jul 18, 2026

   ContributorAuthor

   More actions

   Blocked — this is the consequence step, not startable work. It can only begin once the fixes it re-states against merge upstream:

   • transaction: resolve orphaned locks whose primary was never written tikv/client-rust#544 (G-0001 orphaned-lock fix) — OPEN, mergeable, awaiting lgtm/approval
   • transaction: clear prewrite locks on rollback of a failed pessimistic commit tikv/client-rust#547 (pessimistic rollback) — OPEN, mergeable, approved but needs lgtm re-added after its rebase

   When #544 merges, this fires: bump pins.toml client_rust.rev; make ledger XCONVERGEs on G-0001 (the designed signal); re-state that entry as expect = "agrees" / status = "FIXED"; flip wyrd-gate's d6 XFAIL (and d7 once #547 lands); confirm G-0002 still XDIVERGE; and pick up tikv/client-rust#548/#549 (already merged) in the same pin move. Removing the label is the trigger.
4. eduralph commented on Sep 11, 2026

   

   eduralph

   on Sep 11, 2026

   ContributorAuthor

   More actions

   Status 2026-09-11 — blocked on #544 alone. tikv/client-rust#547 merged 2026-07-22, so only G-0001's fix (#7) is outstanding.

   The move has grown since this was filed: between the pin (e53837d) and master, upstream merged #548, #549, #547, #553, #550, #556, #555, #554 and #562. The re-statement should re-check every declared ledger row, not only the ones expected to converge.