fix(ci): make release gates DIND-compatible
Managed validation / full (pull_request) Successful in 49s
GeoIntel release gates / Python and npm vulnerability policy (pull_request) Successful in 1m30s
GeoIntel release gates / Compile, test, contracts and builds (pull_request) Failing after 2m27s
GeoIntel release gates / GIS image, SBOM and container scan (pull_request) Successful in 4m28s
Managed validation / full (pull_request) Successful in 49s
GeoIntel release gates / Python and npm vulnerability policy (pull_request) Successful in 1m30s
GeoIntel release gates / Compile, test, contracts and builds (pull_request) Failing after 2m27s
GeoIntel release gates / GIS image, SBOM and container scan (pull_request) Successful in 4m28s
This commit is contained in:
@@ -1097,7 +1097,7 @@ A regional run holds tens of thousands of detections, and these are the
|
||||
endpoints the results table and the map overlay call after every run; they
|
||||
previously returned all of them.
|
||||
|
||||
### GET `/api/v1/projects/{project_id}/quality-checks/{id}/evidence/geojson`
|
||||
### GET `/api/v1/projects/{project_id}/quality-checks/{quality_check_id}/evidence/geojson`
|
||||
|
||||
Returns the reviewable geometry behind one quality check: the objects the model
|
||||
missed, the ones it found without a reference, and the confirmed matches.
|
||||
@@ -1863,7 +1863,7 @@ Each feature includes:
|
||||
|
||||
Returns persisted detections for a dataset as a GeoJSON FeatureCollection. Optional filters match the detection list endpoint.
|
||||
|
||||
### GET `/api/v1/projects/{project_id}/quality-checks/{id}/reviews`
|
||||
### GET `/api/v1/projects/{project_id}/quality-checks/{quality_check_id}/reviews`
|
||||
|
||||
Returns the evidence queue plus a `summary`, which now carries
|
||||
`reviewed_metrics`: the score with the operator's verdicts applied, next to the
|
||||
@@ -2084,6 +2084,8 @@ Request:
|
||||
|
||||
Fixture segmenter mode is test/demo-only. It persists only explicit `parameters_json.fixture_segmentations` entries when `parameters_json.fixture_mode=true`; it is never invoked automatically and does not represent production inference.
|
||||
|
||||
### POST `/api/v1/segmentation/run-async`
|
||||
|
||||
The production frontend uses `POST /api/v1/segmentation/run-async`, then polls
|
||||
`GET /api/v1/projects/{project_id}/jobs/{job_id}` and reconciles the terminal
|
||||
job with its persisted `AnalysisRun` and polygon records. It does not fall back
|
||||
|
||||
Reference in New Issue
Block a user