You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(ci): remove retired agentx-v1 database as an ingest target (#550)
The agentx-v1 staging Neon DB held agentic-traces benchmark results
during the AgentX rollout. Its data was migrated into the main
production DB on 2026-07-10 and the staging DB is being retired, so
all ingests (including agentic) now target the production database.
- ingest-agentic-results.yml: drop the agentx-v1 database-target
choice, its DATABASE_AGENTX_V1_WRITE_URL secret wiring, and the
agentx-v1 case branch; production/dev targets are unchanged.
- .claude/agents/ingest.md: reframe the manual-ingest agent doc
around the production DB and its cache-invalidate endpoint instead
of the feat/agentx preview deployment. The "write URL must be
provided by the invoker" safety rule is unchanged.
The DATABASE_AGENTX_V1_WRITE_URL repo secret can be deleted from
GitHub settings once this lands (not possible from code).
中文:移除已退役的 agentx-v1 数据库入库目标。该暂存 Neon 数据库曾在
AgentX 上线期间存放 agentic-traces 基准测试结果,其数据已于
2026-07-10 迁移至主生产数据库,此后所有入库(包括 agentic)均直接
写入生产数据库。本次删除 ingest-agentic-results.yml 中的 agentx-v1
目标选项、对应 secret 及 case 分支,并将手动入库 agent 文档改为面向
生产数据库;production/dev 目标保持不变。合并后可在 GitHub 设置中
删除 DATABASE_AGENTX_V1_WRITE_URL secret。
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .claude/agents/ingest.md
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
name: ingest
3
-
description: Ingest a benchmark run from GitHub Actions into the Neon DB used by the feat/agentx deployment. The target DB write URL must be provided in the invocation. Handles standard ingest, delete+reingest, and changelog entries. Invoke when the user asks to ingest a workflow run URL.
3
+
description: Ingest a benchmark run from GitHub Actions into the Neon DB backing this dashboard. The target DB write URL must be provided in the invocation. Handles standard ingest, delete+reingest, and changelog entries. Invoke when the user asks to ingest a workflow run URL.
4
4
tools: Bash, Read, Edit, Write
5
5
---
6
6
7
-
You ingest benchmark runs from `SemiAnalysisAI/InferenceX` GitHub Actions into the Neon branch used by the `feat/agentx` deployment of this dashboard. Operate on `/Users/quilicic/InferenceX-app`.
7
+
You ingest benchmark runs from `SemiAnalysisAI/InferenceX` GitHub Actions into the Neon DB backing this dashboard. All benchmark types — including agentic — live in the main production DB (the separate agentx-v1 staging DB was retired on 2026-07-10 after its data was migrated to production). Operate on `/Users/quilicic/InferenceX-app`.
8
8
9
9
## Environment
10
10
@@ -13,7 +13,7 @@ You ingest benchmark runs from `SemiAnalysisAI/InferenceX` GitHub Actions into t
13
13
- Use the **direct (non-pooled)** host for ingest/migrations — no `-pooler` in the hostname.
14
14
- For psql diagnostics you may use the same URL directly: `psql "$DATABASE_WRITE_URL" -c "..."`.
15
15
-**Local dev server**: usually `http://localhost:3002` (port 3000 is a different project on this machine — never purge port 3000)
--yes -- -sS -X POST -H "Authorization: Bearer $SECRET"
44
-
rm -rf /tmp/vp
38
+
# Production
39
+
curl -sS -X POST -H "Authorization: Bearer $SECRET" https://inferencex.semianalysis.com/api/v1/invalidate
45
40
```
46
41
47
42
## Delete + reingest (use only when user explicitly says "delete and reingest" OR when the run supersedes prior data with the same (model, hw, framework, precision))
@@ -171,7 +166,7 @@ If the user doesn't specify a description, DO NOT skip the entry and DO NOT bloc
171
166
3.**Ingest** via the standard path. Do NOT use AIPerf tagging unless the user explicitly asks for a separate legend line.
172
167
4.**Refresh materialized view**.
173
168
5.**Add changelog entry — ALWAYS, MANDATORY.** Every ingest gets exactly one changelog entry (see "Adding a perf changelog entry — MANDATORY"). Use the user's text if given (substituting `<SKU>`); otherwise derive one from the run name and add it anyway. Never skip this step.
174
-
6.**Purge both caches** (localhost 3002 + preview — never port 3000).
169
+
6.**Purge both caches** (localhost 3002 + production — never port 3000).
175
170
7.**Report** the row count, date, hardware, run id, and the changelog id (always present).
0 commit comments