tlongwell-blockandEva 8ff38c07bf test(e2e): seed community before relay boot in desktop e2e integration ...

The desktop e2e integration relay-boot still used BUZZ_AUTO_MIGRATE with no
pre-boot community seed, so the channel reconciler bound the deployment
community ONCE at boot (outside its retry loop) before setup-desktop-test-data.sh
seeded it, hit UnmappedHost, and exited permanently. The reconciler's retry
loop only covers late-seeded channels, not a late-seeded community — so the
9 seeded channels were never reconciled and 'loads channels from the relay'
saw 0 channels (60s timeout). Both Desktop E2E Integration shards red.

Mirror the proven backend-integration ordering: apply schema + seed the
localhost:3000 community BEFORE the relay starts, and drop BUZZ_AUTO_MIGRATE
(schema is now applied pre-boot). setup-desktop-test-data.sh's own idempotent
community seed becomes a no-op; its channel INSERTs are then picked up by the
reconciler's retry loop.

Co-authored-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@sprout-oss.stage.blox.sqprod.co>
Signed-off-by: tlongwell-block <109685178+tlongwell-block@users.noreply.github.com>

2026-06-26 21:58:31 -04:00

..

ISSUE_TEMPLATE

Initial commit

2026-03-06 21:00:58 +00:00

workflows

test(e2e): seed community before relay boot in desktop e2e integration

2026-06-26 21:58:31 -04:00

CODEOWNERS

refactor: rename sprout backend to buzz (#958)

2026-06-10 19:29:51 -04:00