milestone 33: contract closure — samples, file-authority enumeration, dead code, bundle ceiling
Gates / frontend (push) Successful in 1m34s
Gates / test (push) Successful in 2m3s
Gates / test-aarch64 (push) Failing after 3h13m33s
Gates / package (push) Successful in 5m20s
Gates / container (push) Successful in 15s
CI / gates (push) Failing after 6h30m45s
Gates / frontend (push) Successful in 1m34s
Gates / test (push) Successful in 2m3s
Gates / test-aarch64 (push) Failing after 3h13m33s
Gates / package (push) Successful in 5m20s
Gates / container (push) Successful in 15s
CI / gates (push) Failing after 6h30m45s
This commit is contained in:
+9
-25
@@ -266,9 +266,12 @@ paths:
|
||||
summary: Live query stream (server-sent events)
|
||||
description: |
|
||||
`text/event-stream`. The stream opens with `retry: 3000`, then sends
|
||||
one `event: query` frame per resolved query whose `data:` line is a
|
||||
`Provenance` object — the body of `/api/queries/{id}` without its `id`,
|
||||
which does not exist yet because the entry precedes its own insert.
|
||||
one `event: query` frame per resolved query. The `data:` line is one
|
||||
query fully explained, in the order a query meets the pipeline: the six
|
||||
objects `QueryDetail` documents — `request`, `group`, `policy`,
|
||||
`rewrites`, `route`, `response` — all of them required, and without
|
||||
that schema's `id`, which does not exist yet because the entry precedes
|
||||
its own insert.
|
||||
A `: ping` comment goes out every 15 seconds.
|
||||
A client that falls more than 64 events behind is disconnected and
|
||||
should re-sync via `/api/queries` after reconnecting. Connections
|
||||
@@ -2166,31 +2169,12 @@ components:
|
||||
type: integer
|
||||
nullable: true
|
||||
|
||||
Provenance:
|
||||
type: object
|
||||
description: |
|
||||
One query, fully explained, in the order a query meets the pipeline. The
|
||||
`data:` payload of a live-stream `event: query` frame is exactly this.
|
||||
required: [request, group, policy, rewrites, route, response]
|
||||
properties:
|
||||
request:
|
||||
$ref: "#/components/schemas/ProvenanceRequest"
|
||||
group:
|
||||
$ref: "#/components/schemas/ProvenanceGroup"
|
||||
policy:
|
||||
$ref: "#/components/schemas/ProvenancePolicy"
|
||||
rewrites:
|
||||
$ref: "#/components/schemas/ProvenanceRewrites"
|
||||
route:
|
||||
$ref: "#/components/schemas/ProvenanceRoute"
|
||||
response:
|
||||
$ref: "#/components/schemas/ProvenanceResponse"
|
||||
|
||||
QueryDetail:
|
||||
type: object
|
||||
description: |
|
||||
`Provenance` plus the row id. Written out rather than composed with
|
||||
`allOf` so the drift guard reads one property list per schema.
|
||||
One query, fully explained, in the order a query meets the pipeline,
|
||||
plus the row id. Written out rather than composed with `allOf` so the
|
||||
drift guard reads one property list per schema.
|
||||
required: [id, request, group, policy, rewrites, route, response]
|
||||
properties:
|
||||
id: { type: integer }
|
||||
|
||||
Reference in New Issue
Block a user