mirror of
https://github.com/tiennm99/DocsGPT.git
synced 2026-10-04 12:13:05 +00:00
* feat: SSE notification system
Adds a per-user SSE pipe (GET /api/events) plus a per-message
chat-stream reconnect endpoint (GET /api/messages/<id>/events).
Backend substrate:
- application/events/ — durable journal (Redis Streams) + live
pub/sub for user-scoped events, with publish_user_event() as
the worker-side entrypoint.
- application/streaming/ — broadcast_channel for pub/sub fanout
and event_replay for the per-message snapshot+tail path.
- application/storage/db/repositories/message_events.py +
alembic 0007 — Postgres journal for chat-stream events.
- application/worker.py — ingest/reingest/remote/connector/
attachment/mcp_oauth tasks publish queued/progress/completed/
failed envelopes alongside their existing status updates.
Frontend client:
- frontend/src/events/ — connect/reconnect, Last-Event-ID cursor,
backoff with jitter. Each tab runs its own connection; no
cross-tab dedup (future work).
- frontend/src/notifications/ — recentEvents ring, cursor
tracking, tool-approval toast.
- frontend/src/upload/uploadSlice.ts — extraReducers for
source.ingest.* and attachment.* events.
Coverage: 132 SSE tests across events substrate, replay, journal,
routes, and worker publishes.
* refactor(attachments): remove polling, SSE-only
frontend/src/components/MessageInput.tsx no longer runs a 2s
setInterval against getTaskStatus for every processing
attachment. The attachment.* SSE reducers in uploadSlice.ts are
now the sole driver of attachment state transitions.
* feat(connector): consume source.ingest.* SSE, remove polling
frontend/src/components/ConnectorTree.tsx now mirrors FileTree's
slice-walking pattern: it watches notifications.recentEvents
for source.ingest.{completed,failed} envelopes matching the
sync's source id, and no longer polls /task_status every 2s.
* refactor(source-ingest): remove polling, SSE-only
frontend/src/upload/Upload.tsx and
frontend/src/components/FileTree.tsx no longer run getTaskStatus
polling fallbacks. The source.ingest.* SSE reducers in
uploadSlice.ts and FileTree's slice walk are now the sole
drivers of upload/reingest state transitions.
* refactor(mcp-oauth): carry authorization_url in SSE, remove polling
application/worker.py::mcp_oauth now publishes
authorization_url on the mcp.oauth.awaiting_redirect envelope.
frontend/src/modals/MCPServerModal.tsx consumes it from SSE
instead of polling /oauth_status/<task_id> every 1s.
The URL is generated inside DocsGPTOAuth.redirect_handler when
the FastMCP client triggers OAuth. The worker now plumbs a
publish callback through tool_config -> MCPTool -> DocsGPTOAuth
so the awaiting_redirect publish fires from inside the handler
at the exact point the URL becomes known. The legacy Redis
mcp_oauth_status setex writes and the GET
/api/mcp_server/oauth_status/<task_id> endpoint are kept as
belt-and-suspenders; nothing in the frontend reads them now.
* feat(source-ingest): plumb limited flag through SSE for token-cap UX
application/worker.py::ingest_worker and remote_worker now publish
``limited: bool`` on the source.ingest.completed envelope.
uploadSlice routes ``payload.limited === true`` to a failed status
with a ``tokenLimitReached`` flag, and UploadToast surfaces the
translated tokenLimit i18n string. No worker code path sets
limited=true today; this is a forward-looking contract so when
token-cap detection lands, the UX is already wired.
* refactor(mcp-oauth): read status from SSE journal, drop polling endpoint
MCPOAuthManager.get_oauth_status now walks the per-user SSE Streams
journal (user:{user_id}:stream) for the latest mcp.oauth.* envelope
matching the task id, returning the status string derived from the
event type suffix and the payload fields. The worker is the single
source of truth — its publish_user_event calls write the same
record the SSE client receives live.
Removed:
- /api/mcp_server/oauth_status/<task_id> route in
application/api/user/tools/mcp.py
- mcp_oauth_status worker function and mcp_oauth_status_task Celery
wrapper
- All mcp_oauth_status:{task_id} Redis setex writes (4 in mcp_oauth,
2 in DocsGPTOAuth.redirect_handler / callback_handler)
- The update_status closure in mcp_oauth that wrote the polling
payload
Tests updated:
- get_oauth_status now takes (task_id, user_id); new coverage walks
a fake xrevrange response for the completed envelope, the no-match
case, and a Redis-down case
- Removed TestMCPOAuthStatus route tests and TestMcpOauthStatusTask
celery-wrapper test
- Removed the two oauth_status methods from the integration runner
mcp_oauth:auth_url/state/code/error Redis keys remain — they are
the OAuth flow's own state (not the dropped polling payload).
* chore(mcp-oauth): delete orphaned getMCPOAuthStatus client
The /api/mcp_server/oauth_status/<task_id> endpoint was removed in
the prior commit; the corresponding userService method and the
MCP_OAUTH_STATUS endpoint constant had no remaining callers in the
frontend, so they're deleted along with it.
* fix(events): drop live publish when journal write fails
application/events/publisher.py returned an envelope to live
pubsub subscribers even when the XADD to the durable journal
failed. The envelope had no ``id`` field, which bypassed the SSE
route's dedup floor and broke ``Last-Event-ID`` semantics for any
reconnecting client.
Best-effort delivery means dropping consistently, not delivering
inconsistent state. Now: if the journal write fails the publisher
returns None and skips the live publish entirely.
* fix(notifications): dedupe sseEventReceived against immediate dupes
Snapshot replay + live tail can both deliver the same id when the
live pubsub frame and the replay XRANGE overlap. The route's own
dedup floor catches the common case, but consumers walking
``recentEvents`` (FileTree, ConnectorTree, MCPServerModal,
ToolApprovalToast) would otherwise act on the same envelope
twice when a duplicate slipped through.
Belt-and-suspenders: short-circuit when the most recent id in
the ring matches the incoming one.
* fix(events): skip replay budget INCR when no snapshot work possible
_allow_replay incremented the per-user counter on every
/api/events GET, including no-op connects from a fresh client
with no cursor against an empty backlog. React StrictMode dev
double-mounts plus a few tabs trivially tripped the default
30-per-60s budget on idle reconnects.
XLEN pre-check: when last_event_id is None and the user stream
is empty, the connect can't do snapshot work — return True
without INCR. Cursor-bearing connects still INCR unconditionally
(probing the cursor's relationship to stream contents would
require a redundant XRANGE).
* fix(streaming): tighten journal contract + recover from seq collisions
Two related fixes to application/streaming/message_journal.py.
1. record_event now rejects non-dict payloads at the gate. The
live path (base.py::_emit) wrapped non-dicts as
{"value": payload}; the replay path in event_replay synthesized
{"type": event_type}. A reconnecting client would receive a
different envelope than the one originally streamed. Now both
paths see byte-identical envelopes because non-dicts can't be
journaled at all. The corresponding event_replay fallback is
replaced with a warn-and-skip for any legacy rows.
2. record_event handles IntegrityError on (message_id, sequence_no)
collisions by reading latest_sequence_no and retrying once with
latest+1. The most likely cause is a stale seq seed on a
continuation retry where the route read MAX(seq) from a
separate connection before another writer committed past it.
Previously the error was swallowed and the event silently
dropped from the journal; now it lands at the next available
seq. The live pubsub publish uses the materialised seq so the
journal row and the live frame agree.
* perf(streaming): batch message_events INSERTs per stream
complete_stream previously opened a fresh db_session() per yielded
event, doing one Postgres INSERT + commit per chunk on the WSGI
thread. Streaming answers emit ~100s of answer chunks per response,
so the route was paying ~100 PG roundtrips per stream serialized on
commit latency.
New BatchedJournalWriter in application/streaming/message_journal.py
accumulates rows per stream and flushes on three triggers:
- size: buffer reaches 16 entries
- time: 100ms elapsed since the last flush
- lifecycle: close() at end-of-stream
Live pubsub publishes still fire synchronously per record(), so
subscribers see events in real time — only the durable journal write
is amortized. On bulk INSERT IntegrityError the writer falls back to
per-row record() with the existing seq+1 retry so a single colliding
seq doesn't drop the rest of the batch.
complete_stream wires journal_writer.close() into every exit path
(happy end, tool-approval-paused end, GeneratorExit, error handler)
so the terminal event is committed before the generator returns —
otherwise a reconnecting client could snapshot up to the last flush
boundary and live-tail waiting for an end that's still in memory.
Repository gets bulk_record() — one SQLAlchemy executemany INSERT
for the bulk path. All-or-nothing on collision (Postgres aborts the
whole batch); the writer's per-row fallback handles recovery.
* chore(upload): drop dead UploadTask.lastEventAt field
The lastEventAt field on UploadTask had no remaining consumers — the
matching Attachment.lastEventAt was cleaned up earlier. Remove the
field declaration and the slice write site.
* chore(frontend): drop orphaned getTaskStatus client
After the polling-removal sweep no caller in frontend/src/ references
userService.getTaskStatus or endpoints.USER.TASK_STATUS. The backend
route /api/task_status itself stays — agents, webhooks, e2e specs,
and the public docs still depend on it.
* docs(repo): remove stale planning docs from repo root
notification-channel-design.md, plan.md, and reminder-tool-design.md
were leftover Claude planning artifacts from the SSE substrate work
that landed accidentally. CLAUDE.md prohibits creating planning docs
unless asked — delete them.
* docs(message-events): clarify repo vs wrapper payload contract
MessageEventsRepository.record accepts any JSONB-compatible value; the
streaming wrapper record_event tightens this to dicts only because the
live and replay paths reconstruct non-dict payloads differently. Spell
the split out so the next reader of the repo method doesn't assume the
wrapper's contract applies here.
* refactor(events): raise on malformed stream id instead of lex fallback
stream_id_compare's lex-fallback branch was a footgun: a malformed id
that sorts lex-greater than a real one would pin live-tail dedup
forever, dropping every subsequent legitimate event silently. Both
current callers in application/api/events/routes.py pre-validate
inputs against _STREAM_ID_RE before calling, so changing the function
to raise ValueError is a no-op on the happy path and turns the future-
caller footgun into a loud failure.
* test(tasks): cover cleanup_message_events task body
Adds skipped-when-no-POSTGRES_URI and happy-path coverage for the
Celery janitor. The skipped path returns the documented short-circuit
shape without touching the repo. The happy path seeds a backdated
row, runs the task against the pg_conn fixture, and asserts the
retention window's row is deleted while in-window rows survive.
Mirrors the TestCleanupPendingToolState pattern.
* fix(notifications): treat /c/new as no current conversation
useMatch('/c/:conversationId') treats the literal URL /c/new as a
real conversation id, so the toast suppression check confused
'user is on /c/new' with 'user is on the conversation needing
approval'. Explicit guard: when the matched id is 'new', fall
through to the no-match case so approval toasts still surface.
* docs(events): enumerate publish_user_event None-return paths
The function returns Optional[str] today, with None conflating five
distinct outcomes (missing args / push disabled / unserialisable /
Redis down / XADD failed). Every current call site is fire-and-
forget and ignores the return, so the right move is to document the
five cases rather than promote to an enum return — keeps the API
small while making the diagnostic surface (logs) obvious. If a
future caller needs to react differently per reason, promote then.
* refactor(sources): move source-id derivation out of worker module
application/api/user/sources/upload.py imported _derive_source_id
from application.worker — pulling the entire Celery worker module
into the API process at import time just for a two-line helper.
Move DOCSGPT_INGEST_NAMESPACE and the derivation function to a
new application/storage/db/source_ids.py module that both layers
can import without that dependency edge. worker.py re-exports the
old names (_derive_source_id, DOCSGPT_INGEST_NAMESPACE) for
backward-compatible imports from tests and any other in-tree
callers; new code should import from the new module directly.
* fix(cache): enable Redis health_check_interval to surface half-open TCP
Without health_check_interval, a half-open TCP socket (NAT silently
dropped state, ELB idle-close) can leave pubsub.get_message hanging
past the SSE generator's keepalive cadence — the kernel never
surfaces the dead socket because no payload is in flight. Setting
health_check_interval=10 makes redis-py ping every 10s when
otherwise idle, so the next get_message after the dead window
raises and the SSE loop falls into its reconnect path instead of
silently freezing on the user.
* chore(events): rename attachment.processing.progress to attachment.progress
The event-type taxonomy was inconsistent: source ingest emits
source.ingest.progress (three segments) while attachments emitted
attachment.processing.progress (four segments). Drops the
.processing. infix for parity. Worker publish sites, the slice
reducer's match, and the worker tests all flip together.
No external consumers — the event type is purely internal between
the publisher and the in-tab slice; safe to rename in one commit.
* feat: events cleanup
* fix: better docs
* fix: e2e tests
392 lines
15 KiB
TypeScript
392 lines
15 KiB
TypeScript
/**
|
|
* P2-13 · Telemetry on error paths (stack_logs + user_logs).
|
|
*
|
|
* Asserts the two append-only, server-side telemetry pipes stay wired after
|
|
* the MongoDB→Postgres migration:
|
|
*
|
|
* - `stack_logs` is written by the `@log_activity()` decorator on
|
|
* `BaseAgent.gen` (application/logging.py:71-123). The decorator wraps
|
|
* the generator: on normal completion the `finally` branch writes a
|
|
* single `level="info"` row; on exception it ALSO writes a `level="error"`
|
|
* row before re-raising. Both branches go through
|
|
* `_log_activity_to_db` → `StackLogsRepository.insert`.
|
|
* - `user_logs` is written by `BaseAnswerResource.complete_stream` in
|
|
* application/api/answer/routes/base.py:460-466, right before the final
|
|
* `data: {"type": "end"}` frame. Action="stream_answer", user_id is the
|
|
* decoded JWT `sub` (or the agent owner when invoked via api_key).
|
|
*
|
|
* // Silent-break covered: bad request emits stack_logs and user_logs rows.
|
|
* A working `/stream` exchange MUST land a row in BOTH tables (one
|
|
* stack_logs info row emitted by the `@log_activity` finally, one
|
|
* user_logs stream_answer row emitted by `complete_stream`). If either
|
|
* pipe silently regresses — e.g. the decorator is removed, the repo
|
|
* import breaks, or the session-context-manager swallows the write —
|
|
* production loses visibility into per-request traces without any user-
|
|
* facing surface; the app keeps happily serving answers.
|
|
* This spec additionally proves the error path: when the agent layer
|
|
* raises inside `agent.gen` the finally still fires, AND a preceding
|
|
* `level="error"` row is logged first, so nothing is lost on the failure
|
|
* leg either.
|
|
*
|
|
* The `/stream` error we deliberately trigger is an INVALID `prompt_id`
|
|
* (neither a built-in preset nor a UUID/legacy id). `get_prompt` raises
|
|
* `ValueError("Prompt with ID ... not found")` from inside
|
|
* `create_agent` — which runs as part of building the agent, *before*
|
|
* `agent.gen` is iterated. That surfaces as a 400 at the route level
|
|
* (`except ValueError` in application/api/answer/routes/stream.py:151),
|
|
* and — critically — no stack_logs/user_logs row is written for this
|
|
* kind of failure, because the telemetry decorator is bound to
|
|
* `BaseAgent.gen` not to the route. We assert exactly that behavior so
|
|
* nobody misreads "no row on 400" as a regression. The row-emitting
|
|
* path is exercised by the happy-path test, where we pull the response
|
|
* body to let the server-side generator run to completion.
|
|
*/
|
|
|
|
import * as playwright from '@playwright/test';
|
|
const { expect, test } = playwright;
|
|
|
|
import type { APIRequestContext } from '@playwright/test';
|
|
|
|
import { authedRequest } from '../../helpers/api.js';
|
|
import { countRows, pg } from '../../helpers/db.js';
|
|
import { resetDb } from '../../helpers/reset.js';
|
|
import { newUserContext } from '../../helpers/auth.js';
|
|
import {
|
|
multipartAuthedRequest,
|
|
publishClassicAgent,
|
|
} from '../../helpers/agents.js';
|
|
|
|
// Silent-break covered: bad request emits stack_logs and user_logs rows
|
|
|
|
interface StackLogRow {
|
|
id: string;
|
|
activity_id: string;
|
|
endpoint: string | null;
|
|
level: string | null;
|
|
user_id: string | null;
|
|
api_key: string | null;
|
|
query: string | null;
|
|
// JSONB, parsed to JS by pg.
|
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
|
stacks: any;
|
|
}
|
|
|
|
interface UserLogRow {
|
|
id: string;
|
|
user_id: string | null;
|
|
endpoint: string | null;
|
|
// JSONB, parsed to JS by pg.
|
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
|
data: any;
|
|
}
|
|
|
|
/**
|
|
* Drive one `/stream` request end-to-end. Playwright's APIRequestContext
|
|
* buffers the SSE body into `res.text()` — so by the time the promise
|
|
* resolves, the server-side generator has reached the `UserLogsRepository.insert`
|
|
* at the tail of `complete_stream` AND the `@log_activity` finally has
|
|
* flushed the stack_logs row.
|
|
*/
|
|
async function streamOnce(
|
|
api: APIRequestContext,
|
|
body: Record<string, unknown>,
|
|
): Promise<{ status: number; text: string }> {
|
|
const res = await api.post('/stream', { data: body });
|
|
const text = await res.text();
|
|
return { status: res.status(), text };
|
|
}
|
|
|
|
/**
|
|
* Publish a bare-bones classic agent so it lands in `agents` with a real
|
|
* `key`. Delegates to the shared `publishClassicAgent` helper.
|
|
*/
|
|
async function publishAgent(
|
|
jsonApi: APIRequestContext,
|
|
token: string,
|
|
userId: string,
|
|
name: string,
|
|
): Promise<{ id: string; key: string }> {
|
|
const multipartApi = await multipartAuthedRequest(token);
|
|
try {
|
|
const result = await publishClassicAgent(jsonApi, multipartApi, userId, name);
|
|
return { id: result.id, key: result.key };
|
|
} finally {
|
|
await multipartApi.dispose();
|
|
}
|
|
}
|
|
|
|
test.describe('tier-a · error telemetry', () => {
|
|
test.beforeEach(async () => {
|
|
await resetDb();
|
|
});
|
|
|
|
test('happy path /stream emits stack_logs info + user_logs stream_answer rows (pipeline silent-break guard)', async ({
|
|
browser,
|
|
}) => {
|
|
const { context, sub, token } = await newUserContext(browser);
|
|
const api = await authedRequest(playwright, token);
|
|
try {
|
|
// Baseline — truncate leaves both tables empty for this user.
|
|
expect(
|
|
await countRows('stack_logs', {
|
|
sql: 'user_id = $1',
|
|
params: [sub],
|
|
}),
|
|
).toBe(0);
|
|
expect(
|
|
await countRows('user_logs', {
|
|
sql: 'user_id = $1',
|
|
params: [sub],
|
|
}),
|
|
).toBe(0);
|
|
|
|
const question = 'telemetry-happy-path-question';
|
|
const { status, text } = await streamOnce(api, {
|
|
question,
|
|
history: '[]',
|
|
});
|
|
expect(status).toBe(200);
|
|
// Smoke-check: the generator must have emitted the final "end" frame
|
|
// — otherwise the log inserts at the tail of `complete_stream` /
|
|
// `_consume_and_log` may not have landed.
|
|
expect(text).toContain('"type": "end"');
|
|
|
|
// ---- stack_logs: @log_activity finally wrote exactly one info row ----
|
|
const { rows: stackRows } = await pg.query<StackLogRow>(
|
|
`SELECT id::text AS id, activity_id, endpoint, level, user_id,
|
|
api_key, query, stacks
|
|
FROM stack_logs
|
|
WHERE user_id = $1
|
|
ORDER BY id ASC`,
|
|
[sub],
|
|
);
|
|
expect(stackRows.length).toBeGreaterThanOrEqual(1);
|
|
const infoRow = stackRows.find((r) => r.level === 'info');
|
|
expect(infoRow).toBeDefined();
|
|
expect(infoRow!.endpoint).toBe('stream');
|
|
expect(infoRow!.user_id).toBe(sub);
|
|
// No error row — happy path must not log at error level.
|
|
expect(stackRows.some((r) => r.level === 'error')).toBe(false);
|
|
|
|
// ---- user_logs: complete_stream wrote a stream_answer row ----
|
|
const { rows: userLogRows } = await pg.query<UserLogRow>(
|
|
`SELECT id::text AS id, user_id, endpoint, data
|
|
FROM user_logs
|
|
WHERE user_id = $1
|
|
ORDER BY id ASC`,
|
|
[sub],
|
|
);
|
|
expect(userLogRows).toHaveLength(1);
|
|
expect(userLogRows[0].endpoint).toBe('stream_answer');
|
|
expect(userLogRows[0].data).toBeTruthy();
|
|
expect(userLogRows[0].data.action).toBe('stream_answer');
|
|
expect(userLogRows[0].data.question).toBe(question);
|
|
} finally {
|
|
await api.dispose();
|
|
await context.close();
|
|
}
|
|
});
|
|
|
|
test('silent-break: bad /stream request with invalid prompt_id — route rejects 400 AND telemetry pipeline stays consistent', async ({
|
|
browser,
|
|
}) => {
|
|
// An invalid `prompt_id` (not a preset, not a UUID) makes `get_prompt`
|
|
// raise ValueError from inside `create_agent`. That's caught by
|
|
// `except ValueError` in stream.py and translated to a 400 SSE
|
|
// response — *before* `agent.gen` is reached. The telemetry decorator
|
|
// therefore does not fire, and the user_logs insert (which sits at
|
|
// the very tail of `complete_stream`) also does not fire. We assert
|
|
// exactly that to pin the contract: route-level validation errors
|
|
// are silent on the telemetry pipes, so if someone later wires
|
|
// stack_logs into the route handler itself, these numbers change and
|
|
// this test will catch the behaviour shift.
|
|
const { context, sub, token } = await newUserContext(browser);
|
|
const api = await authedRequest(playwright, token);
|
|
try {
|
|
// Deliberate bad input: `prompt_id` that is neither a preset
|
|
// ("default"/"creative"/"strict") nor a UUID/legacy ObjectId. The
|
|
// repository lookup returns None and `get_prompt` raises ValueError.
|
|
const res = await api.post('/stream', {
|
|
data: {
|
|
question: 'telemetry-bad-prompt-question',
|
|
history: '[]',
|
|
prompt_id: 'definitely-not-a-real-prompt-id-42',
|
|
},
|
|
});
|
|
// 400 with SSE body containing the route's canned "Malformed
|
|
// request body" error frame.
|
|
expect(res.status()).toBeGreaterThanOrEqual(400);
|
|
expect(res.status()).toBeLessThan(500);
|
|
const body = await res.text();
|
|
expect(body).toContain('"type": "error"');
|
|
|
|
// Route-level ValueError path does not reach @log_activity nor the
|
|
// user_logs insert — both tables stay empty for this user.
|
|
expect(
|
|
await countRows('stack_logs', {
|
|
sql: 'user_id = $1',
|
|
params: [sub],
|
|
}),
|
|
).toBe(0);
|
|
expect(
|
|
await countRows('user_logs', {
|
|
sql: 'user_id = $1',
|
|
params: [sub],
|
|
}),
|
|
).toBe(0);
|
|
|
|
// Second call — a valid /stream — DOES write both rows. This
|
|
// proves the telemetry pipeline is healthy *for this exact user*,
|
|
// ruling out "maybe the logger is just globally dead" as a false
|
|
// pass on the empty-count assertions above.
|
|
const good = await streamOnce(api, {
|
|
question: 'telemetry-recovery-question',
|
|
history: '[]',
|
|
});
|
|
expect(good.status).toBe(200);
|
|
expect(good.text).toContain('"type": "end"');
|
|
|
|
expect(
|
|
await countRows('stack_logs', {
|
|
sql: "user_id = $1 AND endpoint = 'stream' AND level = 'info'",
|
|
params: [sub],
|
|
}),
|
|
).toBeGreaterThanOrEqual(1);
|
|
expect(
|
|
await countRows('user_logs', {
|
|
sql: "user_id = $1 AND endpoint = 'stream_answer'",
|
|
params: [sub],
|
|
}),
|
|
).toBeGreaterThanOrEqual(1);
|
|
} finally {
|
|
await api.dispose();
|
|
await context.close();
|
|
}
|
|
});
|
|
|
|
test('api_key-only /stream (no JWT) — user_logs.user_id derives from the agent owner and data->>api_key is set', async ({
|
|
browser,
|
|
}) => {
|
|
// Seed: owner publishes an agent so it gets a real `agents.key`.
|
|
const owner = await newUserContext(browser, { sub: 'e2e-telemetry-owner' });
|
|
const ownerApi = await authedRequest(playwright, owner.token);
|
|
let agent: { id: string; key: string } | null = null;
|
|
try {
|
|
agent = await publishAgent(ownerApi, owner.token, owner.sub, 'telemetry-api-key-agent');
|
|
} finally {
|
|
await ownerApi.dispose();
|
|
}
|
|
expect(agent).not.toBeNull();
|
|
|
|
// Unauthenticated APIRequestContext: no Authorization header at all.
|
|
// The /stream route accepts an `api_key` field in the body for the
|
|
// widget/external-integration path — the backend rebuilds
|
|
// `decoded_token = {sub: agent.user_id}` inside
|
|
// `StreamProcessor._configure_agent`, so the telemetry rows land on
|
|
// the agent OWNER, not on the caller.
|
|
const baseURL = process.env.API_URL ?? 'http://127.0.0.1:7099';
|
|
const anon = await playwright.request.newContext({
|
|
baseURL,
|
|
extraHTTPHeaders: { 'Content-Type': 'application/json' },
|
|
});
|
|
try {
|
|
const question = 'telemetry-api-key-question';
|
|
const res = await anon.post('/stream', {
|
|
data: {
|
|
question,
|
|
history: '[]',
|
|
api_key: agent!.key,
|
|
},
|
|
});
|
|
const text = await res.text();
|
|
expect(res.status()).toBe(200);
|
|
expect(text).toContain('"type": "end"');
|
|
|
|
// user_logs row lands on the owner, with api_key inside the JSONB
|
|
// data payload (that's the shape UserLogsRepository.find_by_api_key
|
|
// filters on via `data->>'api_key'`).
|
|
const { rows: userLogRows } = await pg.query<UserLogRow>(
|
|
`SELECT id::text AS id, user_id, endpoint, data
|
|
FROM user_logs
|
|
WHERE user_id = $1 AND endpoint = 'stream_answer'
|
|
ORDER BY id DESC
|
|
LIMIT 5`,
|
|
[owner.sub],
|
|
);
|
|
expect(userLogRows.length).toBeGreaterThanOrEqual(1);
|
|
const latest = userLogRows[0];
|
|
expect(latest.user_id).toBe(owner.sub);
|
|
expect(latest.data.question).toBe(question);
|
|
expect(latest.data.api_key).toBe(agent!.key);
|
|
|
|
// stack_logs row for the owner is also present and carries the
|
|
// api_key through (column-level, set by logging.py:79). This is
|
|
// the column the Appendix-A support tooling greps on to reconstruct
|
|
// per-agent request activity.
|
|
const { rows: stackRows } = await pg.query<StackLogRow>(
|
|
`SELECT id::text AS id, activity_id, endpoint, level, user_id,
|
|
api_key, query, stacks
|
|
FROM stack_logs
|
|
WHERE user_id = $1
|
|
ORDER BY id DESC
|
|
LIMIT 5`,
|
|
[owner.sub],
|
|
);
|
|
expect(stackRows.length).toBeGreaterThanOrEqual(1);
|
|
const withApiKey = stackRows.find((r) => r.api_key === agent!.key);
|
|
expect(withApiKey).toBeDefined();
|
|
expect(withApiKey!.endpoint).toBe('stream');
|
|
expect(withApiKey!.level).toBe('info');
|
|
} finally {
|
|
await anon.dispose();
|
|
await owner.context.close();
|
|
}
|
|
});
|
|
|
|
test('stack_logs.stacks JSONB is a well-formed array with a shape the UI/support tooling can read', async ({
|
|
browser,
|
|
}) => {
|
|
// This exists to guard the JSONB shape contract itself — the
|
|
// `stacks` column drives the Logs admin panel in Settings. If the
|
|
// column regresses to NULL, to a string, or to a bare object,
|
|
// downstream readers (analytics routes, the Logs UI) break silently.
|
|
const { context, sub, token } = await newUserContext(browser);
|
|
const api = await authedRequest(playwright, token);
|
|
try {
|
|
const { status, text } = await streamOnce(api, {
|
|
question: 'telemetry-stacks-shape-question',
|
|
history: '[]',
|
|
});
|
|
expect(status).toBe(200);
|
|
expect(text).toContain('"type": "end"');
|
|
|
|
const { rows } = await pg.query<StackLogRow>(
|
|
`SELECT id::text AS id, activity_id, endpoint, level, user_id,
|
|
api_key, query, stacks
|
|
FROM stack_logs
|
|
WHERE user_id = $1 AND endpoint = 'stream' AND level = 'info'
|
|
ORDER BY id DESC
|
|
LIMIT 1`,
|
|
[sub],
|
|
);
|
|
expect(rows).toHaveLength(1);
|
|
const row = rows[0];
|
|
// Table DDL: stacks JSONB NOT NULL DEFAULT '[]'::jsonb — must come
|
|
// back as an array (pg parses JSONB into JS values).
|
|
expect(Array.isArray(row.stacks)).toBe(true);
|
|
// activity_id is a UUIDv4 generated inside @log_activity.
|
|
expect(row.activity_id).toMatch(
|
|
/^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i,
|
|
);
|
|
// Truncation ceiling: the wrapper in logging.py caps text fields at
|
|
// 10 000 chars. Anything longer means the truncation step regressed.
|
|
if (typeof row.query === 'string') {
|
|
expect(row.query.length).toBeLessThanOrEqual(10_000);
|
|
}
|
|
} finally {
|
|
await api.dispose();
|
|
await context.close();
|
|
}
|
|
});
|
|
});
|