@plusscommunities/pluss-core-aws 2.0.25-beta.2 → 2.0.25-beta.4

package/helper/hqPublishing.js

@@ -19,7 +19,7 @@
 
 const AWS = require("aws-sdk");
 const moment = require("moment");
-const indexQuery = require("../db/common/indexQuery");
+const indexQueryRecursive = require("../db/common/indexQueryRecursive");
 const updateRef = require("../db/common/updateRef");
 const editRef = require("../db/common/editRef");
 
@@ -41,6 +41,8 @@ const DEFAULT_PROTECTED_FIELDS = [
 	"PublishedToSites",     // HQ-only field; copies don't carry the multi-site list
 	"UnsentNotification",   // each copy's notification state is independent
 	"Deleted",              // cascadeHqRetract is the dedicated path; propagateHqEdit must not touch this
+	"UnixTimestamp",        // per-copy fan-out timestamp; HQ-source MODIFY must not rewind copies' feed position
+	"UnixTimestampReverse", //   ↳ paired with UnixTimestamp; same rationale (used as feed-sort key on community sites)
 ];
 
 // ---------------------------------------------------------------------------
@@ -94,12 +96,18 @@ const findCopiesByHqSourceId = async (
 	if (!hqSourceId) {
 		return [];
 	}
-	const result = await indexQuery(tableName, {
+	// indexQueryRecursive paginates LastEvaluatedKey internally and returns a
+	// flat array — required because a single GSI query response caps at 1 MiB
+	// and large-content HQ fan-outs to ~50 client sites can exceed that. With
+	// the non-recursive indexQuery, propagateHqEdit + cascadeHqRetract would
+	// silently miss copies on page 2+, leaving them stale after edits and
+	// visible after retractions.
+	const items = await indexQueryRecursive(tableName, {
 		IndexName: indexName,
 		KeyConditionExpression: "HqSourceId = :sid",
 		ExpressionAttributeValues: { ":sid": hqSourceId },
 	});
-	return result?.Items || [];
+	return items || [];
 };
 
 /**
@@ -136,7 +144,14 @@ const fanOutHqSource = async (hqSourceRow, tableName) => {
 		return [];
 	}
 	const copyId = `hqcopy-${hqSourceRow.Id}`;
-	const now = moment.utc().unix();
+	// IMPORTANT: milliseconds (.valueOf), not seconds (.unix). Newsletter
+	// rows written by addNewsletterEntry.js use `moment.utc().valueOf()` for
+	// UnixTimestamp. UnixTimestampReverse-keyed feed queries (the standard
+	// Pluss list pattern) would otherwise rank HQ copies ~1000× ahead of
+	// locally-authored posts forever — MAX_SAFE_INTEGER minus a number 10^9
+	// is vastly larger than MAX_SAFE_INTEGER minus 10^12. Keep parity with
+	// the canonical addNewsletterEntry convention.
+	const now = moment.utc().valueOf();
 
 	const writes = targets.map((targetSiteId) => {
 		// Spread + override pattern: keep all content fields, swap identity

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@plusscommunities/pluss-core-aws",
-	"version": "2.0.25-beta.2",
+	"version": "2.0.25-beta.4",
 	"description": "Core extension package for Pluss Communities platform",
 	"scripts": {
 		"betapatch": "npm version prepatch --preid=beta",