You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
reset keeps the wallet-less example's accounts after it drops the ledger #277
pnpm stack reset (pnpm dev:amulet-vesting-walletless reset in this repo) stops the stack and drops the LocalNet's ledger and the Wallet Gateway's stores. The wallet-less example's Postgres survives it: reset runs the app's stack:down, which stops Postgres without -v. Its accounts keep parties that only the dropped ledger had.
The example's README and CLAUDE.md work around it by hand: docker compose -f server/compose.yaml down -v after canton-barebones reset.
Fix: let reset run an optional stack:reset script of the app once the ledger is gone, as up and down already run stack:up and stack:down. The wallet-less example defines it to stop its server and drop the Postgres volume. A failing stack:reset fails reset.
Steps to reproduce
pnpm dev:amulet-vesting-walletless up, then sign up as alice on http://localhost:3012
pnpm dev:amulet-vesting-walletless reset, then up again
Sign in as alice and use Tap Amulet, then try to sign up as alice again
Expected vs actual behavior
Expected: the reset drops the accounts with the ledger, so alice can sign up again;
Actual: alice still signs in, but the account's party is not on the new ledger, so ledger calls fail; signing up as alice returns "that username is taken".
Severity
Low: the README's manual down -v recovers it. It lands with #272; #275's example may keep state beside the ledger too.
Activity