interloper-api 0.21.0__tar.gz → 0.22.0__tar.gz

{interloper_api-0.21.0 → interloper_api-0.22.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: interloper-api
-Version: 0.21.0
+Version: 0.22.0
 Summary: Interloper FastAPI routes
 Author: Guillaume Onfroy
 Author-email: Guillaume Onfroy <guillaume@digitlcloud.com>

{interloper_api-0.21.0 → interloper_api-0.22.0}/pyproject.toml

@@ -3,7 +3,7 @@
 # ###############
 [project]
 name = "interloper-api"
-version = "0.21.0"
+version = "0.22.0"
 description = "Interloper FastAPI routes"
 readme = "README.md"
 authors = [{ name = "Guillaume Onfroy", email = "guillaume@digitlcloud.com" }]

{interloper_api-0.21.0 → interloper_api-0.22.0}/src/interloper_api/routes/runs.py

@@ -3,10 +3,10 @@
 from __future__ import annotations
 
 import datetime as dt
-from typing import Literal
+from typing import Annotated, Literal
 from uuid import UUID
 
-from fastapi import APIRouter, Depends, HTTPException, Response
+from fastapi import APIRouter, Depends, HTTPException, Query, Response
 from interloper.errors import NotFoundError
 from interloper_db import Profile, Store
 from interloper_db.models import Event, Run
@@ -244,23 +244,28 @@ def list_run_events(
     response: Response,
     limit: int = 100,
     offset: int = 0,
-    asset_id: UUID | None = None,
+    asset_id: Annotated[list[UUID] | None, Query()] = None,
+    event_type: Annotated[list[str] | None, Query()] = None,
     user: Profile = Depends(get_current_user),
     store: Store = Depends(get_store),
 ) -> list[EventResponse]:
     """List events for a run, oldest first.
 
     Events are ordered ``timestamp ASC`` and paged with ``limit``/``offset``.
-    ``asset_id`` narrows the listing to one asset's events. The total number
-    of matching events (ignoring ``limit``/``offset``, honouring ``asset_id``)
-    is returned in the ``X-Total-Count`` response header so clients can page
-    through every event — including the terminal/outcome events
+    ``asset_id`` and ``event_type`` may each be repeated to narrow the listing
+    to one or more assets (e.g. every asset sharing a status) and/or event
+    types (e.g. a "Lifecycle"/"Errors"/"Logs" tab); the two compose. The total
+    number of matching events (ignoring ``limit``/``offset``, honouring the
+    filters) is returned in the ``X-Total-Count`` response header so clients can
+    page through every event — including the terminal/outcome events
     (``asset_completed``, ``asset_failed``, ``run_failed``, …) that sort last.
     """
     _load_authorized_run(run_id, user, store)
     limit = max(1, min(limit, MAX_EVENTS_PAGE_SIZE))
     offset = max(0, offset)
-    total = store.count_events(run_id=run_id, asset_id=asset_id)
+    total = store.count_events(run_id=run_id, asset_ids=asset_id, event_types=event_type)
     response.headers["X-Total-Count"] = str(total)
-    events = store.list_events(run_id=run_id, asset_id=asset_id, limit=limit, offset=offset)
+    events = store.list_events(
+        run_id=run_id, asset_ids=asset_id, event_types=event_type, limit=limit, offset=offset
+    )
     return [_event_to_response(e) for e in events]