Artifact [95503c2e70]

Artifact 95503c2e70959090de2e5a3319f5ef435ed2139b64b4ad57fa0ff5fb3f523312:

• File internal/checkout/update_undo_js.go — part of check-in [294a537880] at 2026-10-19 16:10:06 on branch feat/submanifest-reader — fix(checkout): save undo state in Update, as fossil does

  Update saved no undo state, so nothing could reverse it. It now reads the file of every step that writes or removes one before writing, as fossil's update calls undo_save, and saves those files with copies of vfile and vmerge and the checked-out version in the same transaction that moves the checkout to the target. If a write fails partway the files are put back, as fossil's undo_rollback does.

  Checkout.Undo and Checkout.Redo (internal and public) swap that state back and forth and keep checkout-hash naming the restored version. The undo package gains ReadFile, SaveTx and RestoreFiles, and its undo table now has fossil's schema (isExe, unique pathname, rowid order, the executable bit read from disk), so fossil undo reverses a go-libfossil update and Checkout.Undo reverses fossil update; fossil 2.28 interop tests check both. Under js/wasm, which has no undo package, Update saves nothing.

  Tracked in #446 (user: [email protected], size: 446) [annotate] [blame] [check-ins using] [more...]

//go:build js

package checkout

import "database/sql"

// updateUndo is empty under js/wasm, which has no undo package: Update
// saves no undo state there, and cannot put files back after a failure.
type updateUndo struct{}

func (c *Checkout) readUpdateUndo([]updateStep) (updateUndo, error) { return updateUndo{}, nil }

func (updateUndo) save(*sql.Tx) error { return nil }

func (c *Checkout) rollBackUpdate(updateUndo) error { return nil }