Frame the port-drawn gizmo in the CCTV QA drag fixture and share the catalog-pair reader

The drag-fixture framing looked the gizmo up in viewer.entities, which main no
longer populates, so it did nothing and five drag checks stayed inconclusive.
It now reads the arrow from the layer's drawn state and records the framed
shaft length as a check.

Tarktee and Lithuania read their two catalogs through one helper,
readCatalogsTogether, so both get the shared deadline, sibling abort and the
release of a response that arrives after the other feed failed.

An Ontario error response has its body released, and tests pin the refused
redirect and system-code log labels.
This commit is contained in:
Said Turksever committed 2026-11-19 18:06:58 +00:00
1 parent bdd92663d6
commit 75f1a3c181
9 files changed
+160 -92

No files matched your search

+5 -2
View File
@@ -7546,8 +7546,11 @@ silently demoting every later lookup for the session.
have a 4 MiB per-document limit, enforced against declared length and
streamed bytes. A failed request, unsuccessful response or body read aborts
the other feed at once and releases every response body, including one that
arrives after the failure. Cameras sharing an image number are deduplicated
before the Tarktee pack cap is applied.
arrives after the failure. The Lithuania pack reads its two catalogs
through the same helper (`readCatalogsTogether`,
`server/providers/cctv/catalogPair.js`) with its 15 s deadline. An Ontario
error response has its body released. Cameras sharing an image number are
deduplicated before the Tarktee pack cap is applied.
- **CCTV v3 UX — viewshed + calibration gizmo** (built 2026-07-05 and field
validated 2026-07-21): the COVERAGE toggle is a
tri-state cycle `OFF → ON → VIEWSHED`; viewshed mode renders each visible camera's frustum