Skip to content

[Epic] Fix SSE re-emit race after async UPDATEs #654

@jakebromberg

Description

@jakebromberg

Problem

Multiple async post-INSERT UPDATEs on flowsheet rows fire after the synchronous liveFs SSE refetch event. Connected consumers fetch the row before the UPDATE lands, see NULL, and never see a second event. This affects iOS users (tubafrenzy mode, ~100% today) and dj-site once it migrates to SSE.

The fix shape is shared across both children: a resolved-callback mechanism on the fire-and-forget helper that fires after the UPDATE commits with at least one user-visible field non-null, routed through a single in-process notify point that drives the playlist-proxy re-enrich and a richer liveFs broadcast (type='metadata-updated' / 'linkage-updated', with the changed fields).

Children

Both children share the same notify-point machinery; this parent serves as a single tracking entry for the work.

Adjacent

Acceptance

Out of scope

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingepicEpic-level tracking issuekind:epicParent epic issuelmlTouches library-metadata-lookuptubafrenzyTouches WXYC/tubafrenzy (webhook, legacy mirror, flowsheet ETL, reconcile)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions