Skip to content

Commit 5d3525d

Browse files
authored
fix: guard against empty relevantPayloads before querying activityRelations (#4219)
Signed-off-by: Mouad BANI <mouad-mb@outlook.com>
1 parent 5c72640 commit 5d3525d

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

services/apps/data_sink_worker/src/service/activity.service.ts

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -646,6 +646,13 @@ export default class ActivityService extends LoggerBase {
646646
`[ACTIVITY] We still have ${relevantPayloads.length} activities left to process after finding segments!`,
647647
)
648648

649+
// relevantPayloads can be drained to zero by the erasure/segment loop above (e.g. all
650+
// members flagged for erasure). Calling queryActivityRelations with an empty array would
651+
// produce invalid SQL: `timestamp in ()` and a bare `()` group.
652+
if (relevantPayloads.length === 0) {
653+
return resultMap
654+
}
655+
649656
const orConditions = relevantPayloads.map((r) => {
650657
return {
651658
and: [

0 commit comments

Comments
 (0)