@7365admin1/core 3.52.5-staging.250 → 3.52.5

package/CHANGELOG.md

@@ -1,5 +1,57 @@
 # @iservice365/core
 
+## 3.52.5
+
+### Patch Changes
+
+- 9bad426: Revoke each expired vehicle's plate only from its own site's cameras, and fail closed
+
+  The hourly expired-vehicle sweep declared its `siteCameras` array outside the
+  per-vehicle loop and only ever pushed to it, so the list grew as the run went
+  on: the second vehicle was revoked from its own site's cameras AND from the
+  first vehicle's. `recNo` is a per-device sequence number, so those extra calls
+  did not simply miss - they addressed whatever record carried that number on the
+  other site's camera and took an unrelated, still-valid plate off the barrier.
+  Cameras are now resolved per vehicle, cached by site id so each site is still
+  paged only once per run.
+
+  The sweep also marked every expired vehicle deleted with one blanket
+  `updateMany`, regardless of what the cameras answered, so a record could read
+  "deleted" while its plate still opened the gate. Only vehicles whose every
+  camera confirmed are now marked deleted; the rest are left expired, logged at
+  error level naming the vehicle, plate, site and camera, and retried on the next
+  hourly run. `deleteExpiredVehicles` now requires the list of ids.
+
+  Also: each camera is asked for its own record id before the removal (the same
+  thing manual delete does), the ANPR list is chosen from the vehicle's type
+  instead of always TRAFFIC_REDLIST, a site with no ANPR camera no longer aborts
+  the whole run, and the transaction that wrapped nothing - the only write was
+  issued without the session - has been removed.
+
+- 082a865: Fail closed in the visitor ANPR sweep, and remove the dead invitation transaction
+
+  `processTransactionDahuaStatus`, the hourly job that takes an expired or
+  checked-out visitor's plate off the site's ANPR camera, marked the transaction
+  `dahuaSyncStatus: "removed"` on the line after the camera call and only skipped
+  on a thrown error. `removePlateNumber` does not throw for a device failure - it
+  returns an outcome object - so a camera answering 401 or 500, or not answering
+  at all, still had the transaction recorded as removed while the visitor's plate
+  was still on the barrier. Nothing retried it either, because the query that
+  feeds the sweep skips anything already marked removed.
+
+  It now uses the same decision logic as the expired-vehicle sweep: only a
+  transaction every camera confirmed is marked removed, and the rest are logged at
+  error level naming the plate, the site and the camera, then retried on the next
+  run. Each camera is also asked for its own record id before the removal, which
+  is what the old "not found" message sniff was reaching for and what stops a
+  transaction whose record is already gone from being retried for ever.
+
+  `checkExpiredInvitation` opened a session and a transaction and then issued
+  every write without that session, never committing: the transaction protected no
+  write and the rollback rolled back nothing. Each invitation is independent, so
+  there is no invariant spanning them and nothing for a transaction to protect -
+  it is removed rather than wired up.
+
 ## 3.52.4
 
 ### Patch Changes

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@7365admin1/core",
   "license": "MIT",
-  "version": "3.52.5-staging.250",
+  "version": "3.52.5",
   "author": "7365admin1",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/.changeset/expired-vehicle-cron-per-site-fail-closed.md

@@ -1,27 +0,0 @@
----
-"@7365admin1/core": patch
----
-
-Revoke each expired vehicle's plate only from its own site's cameras, and fail closed
-
-The hourly expired-vehicle sweep declared its `siteCameras` array outside the
-per-vehicle loop and only ever pushed to it, so the list grew as the run went
-on: the second vehicle was revoked from its own site's cameras AND from the
-first vehicle's. `recNo` is a per-device sequence number, so those extra calls
-did not simply miss - they addressed whatever record carried that number on the
-other site's camera and took an unrelated, still-valid plate off the barrier.
-Cameras are now resolved per vehicle, cached by site id so each site is still
-paged only once per run.
-
-The sweep also marked every expired vehicle deleted with one blanket
-`updateMany`, regardless of what the cameras answered, so a record could read
-"deleted" while its plate still opened the gate. Only vehicles whose every
-camera confirmed are now marked deleted; the rest are left expired, logged at
-error level naming the vehicle, plate, site and camera, and retried on the next
-hourly run. `deleteExpiredVehicles` now requires the list of ids.
-
-Also: each camera is asked for its own record id before the removal (the same
-thing manual delete does), the ANPR list is chosen from the vehicle's type
-instead of always TRAFFIC_REDLIST, a site with no ANPR camera no longer aborts
-the whole run, and the transaction that wrapped nothing - the only write was
-issued without the session - has been removed.

package/.changeset/visitor-dahua-cron-fail-closed.md

@@ -1,27 +0,0 @@
----
-"@7365admin1/core": patch
----
-
-Fail closed in the visitor ANPR sweep, and remove the dead invitation transaction
-
-`processTransactionDahuaStatus`, the hourly job that takes an expired or
-checked-out visitor's plate off the site's ANPR camera, marked the transaction
-`dahuaSyncStatus: "removed"` on the line after the camera call and only skipped
-on a thrown error. `removePlateNumber` does not throw for a device failure - it
-returns an outcome object - so a camera answering 401 or 500, or not answering
-at all, still had the transaction recorded as removed while the visitor's plate
-was still on the barrier. Nothing retried it either, because the query that
-feeds the sweep skips anything already marked removed.
-
-It now uses the same decision logic as the expired-vehicle sweep: only a
-transaction every camera confirmed is marked removed, and the rest are logged at
-error level naming the plate, the site and the camera, then retried on the next
-run. Each camera is also asked for its own record id before the removal, which
-is what the old "not found" message sniff was reaching for and what stops a
-transaction whose record is already gone from being retried for ever.
-
-`checkExpiredInvitation` opened a session and a transaction and then issued
-every write without that session, never committing: the transaction protected no
-write and the rollback rolled back nothing. Each invitation is independent, so
-there is no invariant spanning them and nothing for a transaction to protect -
-it is removed rather than wired up.