Skip to content

Commit c5dd23c

Browse files
committed
fix(webapp): read the span-panel waitpoint from the owning store
SpanPresenter built WaitpointPresenter with no run-ops read clients, so the trace panel read a NEW-residency waitpoint on the control-plane database and showed "Waitpoint not found". Wire the run-ops read clients like the other split-aware routes.
1 parent 31a632a commit c5dd23c

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

apps/webapp/app/presenters/v3/SpanPresenter.server.ts

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ import {
1010
} from "@trigger.dev/core/v3";
1111

1212
import { AttemptId, getMaxDuration, parseTraceparent } from "@trigger.dev/core/v3/isomorphic";
13+
import { $replica, runOpsNewReplica, runOpsSplitReadEnabled } from "~/db.server";
1314
import {
1415
extractIdempotencyKeyScope,
1516
getUserProvidedIdempotencyKey,
@@ -722,7 +723,11 @@ export class SpanPresenter extends BasePresenter {
722723
return { ...data, entity: null };
723724
}
724725

725-
const presenter = new WaitpointPresenter(undefined, undefined, {});
726+
const presenter = new WaitpointPresenter(undefined, undefined, {
727+
newClient: runOpsNewReplica,
728+
legacyReplica: $replica,
729+
splitEnabled: runOpsSplitReadEnabled,
730+
});
726731
const waitpoint = await presenter.call({
727732
friendlyId: span.entity.id,
728733
environmentId,

0 commit comments

Comments
 (0)