[omegent-app]

Why

Follow-up to #930, found during its Sol review. beginLiveQueryFetch incremented discovering before awaiting source.ready(), but the caller only recorded the result after the await. If a live fetch was interrupted during that await (unmount, superseding refresh), the finalizer ran with false and never decremented. From then on, every repository write was buffered and never dispatched, so all live queries went stale.

What

• liveQueryInvalidation.ts: add a synchronous acquireLiveQueryFetch plus liveQueryReady. beginLiveQueryFetch stays as a deprecated export (it is reachable through the ./* subpath export).
• atomQuery.ts: wrap the live fetch in Effect.acquireUseRelease, so endLiveQueryFetch always gets the acquired token, including after an interrupt or a ready() failure.
• Regression test: mount an observed live query whose source never becomes ready, unmount it, then check that a later write still invalidates another live query. Fails on main, passes here.
• Patch changeset for @effect-app/vue.

---

opened by andreasimonecosta in chat thread Discord · Discord · T3

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/@effect-app/cli@932

effect-app

npm i https://pkg.pr.new/effect-app@932

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/@effect-app/eslint-codegen-model@932

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/@effect-app/eslint-shared-config@932

@effect-app/infra

npm i https://pkg.pr.new/@effect-app/infra@932

@effect-app/vue

npm i https://pkg.pr.new/@effect-app/vue@932

@effect-app/vue-components

npm i https://pkg.pr.new/@effect-app/vue-components@932

commit: 9fa3728