mirror of
https://github.com/block/buzz.git
synced 2026-10-30 05:51:46 +00:00
ac40eb2af9
The shared wholeBlobSync suite's "second edit queued during confirmation survives" test minted the peer winner with an auto-generated peer-N id, which sorts lexicographically above evt-N. remoteAdvancedSince therefore returned false and edit-2 published without either foldSupersedingAttemptWinner repair path firing — both could be removed without failing the test. Restore the explicit "0-peer-winner" id (lexicographically < evt-N), matching the original channelSectionsSync.test.mjs fixture and the other two collision tests in the same shared file. This makes remoteAdvancedSince return true so the stale-gen adoptRemote repair path (line 401) fires on confirmation, and the pre-publish repair path (line 538) acts as the safety net for the retry case. Removing both fold call sites now fails the regression as required. Updated inline comments to describe the corrected execution path. No change to assertions (publishCalls=2, adopted=0, pendingStore=null, outbox=null) or to the fetch sequence. Co-authored-by: Will Pfleger <pfleger.will@gmail.com> Signed-off-by: Will Pfleger <pfleger.will@gmail.com>
Buzz
Desktop chat shell with:
- Tauri + React + TypeScript + Vite
- Tailwind CSS
- shadcn/ui-ready shared components
- Biome (lint/format/check)
- Feature-driven frontend structure
Scripts
pnpm dev- run the web frontendpnpm tauri dev- run the desktop apppnpm build- typecheck and build frontendpnpm typecheck- TypeScript checkspnpm lint- Biome lintpnpm format- Biome format (write)pnpm check- Biome check
Structure
src/shared- reusable app-wide code (ui,lib,styles)src/features- feature modules (vertical slices)src/app- top-level app composition