mirror of https://github.com/azaion/satellite-provider.git synced 2026-06-21 23:31:15 +00:00

Files

T

Oleksandr Bezdieniezhnykh 1802d32107 [AZ-488] UAV tile batch upload + 5-rule quality gate

Replaces the 501 stub at POST /api/satellite/upload with a multipart
batch endpoint that ingests UAV-captured tiles, runs each item through
a 5-rule quality gate, and persists accepted tiles via the AZ-484
multi-source storage path with source='uav'.

Quality gate (in fixed order, first failure wins): JPEG format
(content-type + magic), size band 5 KiB-5 MiB, exact 256x256
dimensions, captured-at age (no future >30 s skew, no older than
7 days), luminance variance on 32x32 downsample. Closed reject-reason
enumeration in v1.0.0 contract.

Authorization: custom PermissionsRequirement / PermissionsAuthorization
Handler that reads the JWT `permissions` claim (tolerates both
repeated-string and JSON-array shapes). Endpoint protected by
RequiresGpsPermission policy; 401 without token, 403 without GPS perm.

Persistence: file-first to ./tiles/uav/{z}/{x}/{y}.jpg, then
ITileRepository.InsertAsync UPSERT (per-source UPSERT contract from
AZ-484). Per-item failures reported in response without aborting the
batch. Kestrel MaxRequestBodySize and FormOptions limits set to
MaxBatchSize x MaxBytes (default 100 x 5 MiB = 500 MiB).

New frozen contract: _docs/02_document/contracts/api/uav-tile-upload.md
v1.0.0. PT-08 NFR added to performance-tests.md as Deferred (harness
work tracked in PT-07 leftover, per AZ-488 § Risk 4).

Tests: 11 quality-gate unit tests, 5 handler unit tests, 3 file-path
unit tests, 12 permission-handler unit tests, 7 integration tests
(AC-1..AC-6, AC-8). All 253 unit tests + smoke integration suite
green.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-11 23:50:49 +03:00

3.4 KiB

Raw Blame History

Leftover — PT-07 perf harness + cycle 1 perf run

Timestamp: 2026-05-11T07:05:00Z
Origin: autodev cycle 1, Step 15 (Performance Test)
Blocker class: non-user-input — work was deferred at the Step 15 user gate; no missing user decision blocks completion.

What was deferred

PT-07 implementation in scripts/run-performance-tests.sh: capture pre-change baseline for GetTilesByRegionAsync p95 latency, run post-change measurement, compute the ratio, and assert ratio ≤ 1.10. PT-07 was recorded as a documentation entry during Step 12 (_docs/02_document/tests/performance-tests.md + traceability-matrix.md "NFRs → Test Mapping" section) but the runner script does not yet have the corresponding scenario.
Active perf run of PT-01..PT-06 against the post-AZ-484 build. The runner exists; it requires docker-compose up on the dev host. Not executed this cycle (per the meta-rule "ask before kicking off Docker / long-running perf operations").

Why it is safe to defer

AZ-484 functional correctness validated by 5 dedicated AZ-484 integration tests (Step 11). The DB read paths exercised by PT-07 are the same ones exercised by MostRecentAcrossSourcesSelection_AZ484_AC2 etc.
The post-AZ-484 SQL uses the same idx_tiles_unique_location_source index as the contract specifies; structurally there is no new full scan, join, or lock added vs. pre-AZ-484.
Cycle 1 perf run is recorded as Unverified (not Fail) per the test-run perf-mode rules — gate does not block deploy.

Replay actions for next /autodev invocation

When the next cycle's autodev runs, before any new tracker write or before re-entering Step 15 in cycle 2:

Add PT-07 to scripts/run-performance-tests.sh:
- Capture a pre-change baseline by checking out the parent of the AZ-484 commit (git rev-parse HEAD~N where N points at the AZ-484 batch), running the existing PT-03/PT-04 region scenarios, and recording the GetTilesByRegionAsync timings (the repository already logs slow query warnings at >500 ms — extend that log line to include median/p95 captured per call window).
- Run the post-change measurement against the current HEAD.
- Compute the p95 ratio and fail when > 1.10.
Bring up the docker stack (docker-compose up --build -d) and run the full perf script with the user's explicit go-ahead.
Capture results into _docs/06_metrics/perf_<YYYY-MM-DD>_cycle<N>.md.
Once results are recorded, delete this leftover file.

AZ-488 follow-on: PT-08 (UAV upload latency)

The AZ-488 commit added PT-08 (UAV tile batch upload latency) to _docs/02_document/tests/performance-tests.md with Status Deferred because it reuses the same harness expansion as PT-07 (baseline capture + p95 ratio). When PT-07's runner-script scenario is implemented in step 1 above, add the PT-08 scenario in the same commit — the integration-test fixtures already exist (SatelliteProvider.IntegrationTests/UavUploadTests happy-path JWT + UavTileImageFactory.CreateRandomJpeg). After PT-08 runs, flip the Status line in performance-tests.md from Deferred to active. This keeps cycle 1 retro Action 2 satisfied for both NFRs.

Tracker action (none required this cycle)

This leftover does NOT require a Jira ticket on its own — it tracks deferred process work, not user-visible scope. If the perf comparison reveals a regression next cycle, that finding will create a Jira bug; until then there is nothing to file.

3.4 KiB Raw Blame History