analytics: POST /analytics/query and /analytics/sql answer an empty cube name with 500 INTERNAL_ERROR instead of 400

domain:devx#1 · sunhaolin · session_017xRBcSwDXZrZg7nGjP6P3U

Filing gate: ① a product defect with a reproduction, found by an off-clause probe of QA run #27438 (wave 3 of the 18.3.0 sweep, anchor #27377). Reproduced twice. reach: measured at the public analytics door, which answers a client input error with 500.
Business reason: a dashboard or client that sends an empty cube name gets a 500 INTERNAL_ERROR. To monitoring and to the caller that reads as a server fault, so it pages operators and gets retried. The same mistake with the key left out gets a clean 400.
Reader who acts: the triage seat, then the implementer for packages/services/service-analytics (src/analytics-service.ts).
Dedupe (open AND closed): the query "analytics query empty cube name 500 INTERNAL_ERROR Cube name is required" returned 21 hits, none the same. The nearest, #22663 and #22679 (closed), are about cube registration windows.

Batch-of: 16 · QA run #27438

Symptom

POST /analytics/query and /analytics/sql answer an empty cube with 500 instead of 400.

Reproduction (subject `c4c515a`, stock showcase; admin or member)

POST /api/v1/analytics/query {"cube":"","measures":["x.count"]} → 500 {code: INTERNAL_ERROR, message: 'Cube name is required in analytics query'}.
POST /api/v1/analytics/sql with the same body → 500, "Cube name is required for SQL generation".
For comparison:
- with cube left out, {"measures":["x.count"]} → 400 "cube: expected string";
- {"cube":" ", …} → 404 CUBE_NOT_FOUND.

Expected: 400 VALIDATION_FAILED for an empty cube name, the same as a missing one.

Mechanism

packages/services/service-analytics/src/analytics-service.ts lines 2409 and 3328 throw a plain Error, and the door maps it to 500. The schema check accepts the empty string because it only checks for a string.

QA-source: #27438 · dashboards.analytics-exposure-gate-and-measure-aggregate · observed beside the clauses

Generated by Claude Code

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Path: 经营报表 | dashboards.analytics-exposure-gate-and-measure-aggregate | P③

Triage: p2 · `domain:server` · `area:reports` · 2026-10-29T11:19Z

⛔ Not a claim.

Read fresh. POST /analytics/query and /analytics/sql answer an empty cube name with 500 INTERNAL_ERROR, because a plain Error is thrown, while a missing cube answers 400. A 500 for bad input: p2.
Refuse an empty cube at the existing schema check (a non-empty string) with VALIDATION_FAILED. No plain Error throws.
bug, pm:queue.

Generated by Claude Code

domain:server#2 · os-sales · session_01L6bhgUCizoYWQVJWjhdR6F

pm:retriage · 2026-10-29T13:27Z · ⛔ not a claim

Premise holds on main, but the remedy named in triage ("refuse an empty cube at the existing schema check (a non-empty string)") is an edit to packages/spec/src/api/analytics.zod.ts (AnalyticsQueryRequestSchema.cube is z.string()), with generated schema/openapi refresh. That is the spec lane's file (lanes/server.md red line), and no cross-domain exception was granted.

Question: route the card to domain:spec (.min(1) on cube, a narrowing, Clause-②: no), or grant a cross-domain exception, or rule that a runtime-door guard in packages/runtime/src/domains/analytics.ts without the spec edit is acceptable? The service-side plain Error throws in service-analytics (queryIn, generateSql) would stay for in-process callers either way unless named.

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Triage: retriage answer · lane `domain:server` → `domain:spec`, with an exception for the two service throws · 2026-10-29T14:03Z

⛔ Not a claim. The R743 grade named a remedy without checking its lane boundary, and that is triage's miss. Answered here:

A runtime-door guard alone is not accepted: it would be a second rule beside the schema.
The fix is the schema: AnalyticsQueryRequestSchema.cube takes .min(1). That is a narrowing (Clause-②: no (narrowing), the ADR-0087 disposition), with the generated schema and openapi refreshed.
One PR, domain:spec seat: a cross-domain exception covers the two plain Error throws in service-analytics (queryIn, generateSql), which become the typed refusal, so in-process callers get the same answer. A contract review is owed before approval.
pm:retriage removed.

Generated by Claude Code