双盲复算前端复核修正(第 1 轮):高亮按服务端真实的差异输出做,「记入数据目录」只在服务端真会写时有条件地说,后果和提示按节点的处置说

审批卡
- 对照两条 SQL:text_diff 是规范化之后的行(列名带表名、条件并成一行),和原文逐行对不上,原来按「两边逐行相等」高亮在真实输出上一处都标不出。改成两段原文按行做一次 LCS(不看空白、大小写和行尾逗号分号)高亮不同的行,一行都对不上时不乱标;text_diff 分原流程、盲算两栏,每行高亮(窄栏上下排)。
- 「只差一个方面、会记入数据目录」:照服务端 dual_check_facts 的门槛收紧——不等价、没用兜底、差异恰好一条(几个输入都对不上时合并后至少两条,所以也就是只有一个输入对不上),且是时间列、筛选条件或聚合;按这三种分别有条件地说会记成哪一项,选「两边都不对」不记、已有人工确认的不覆盖、以时间线为准。时间范围、两条筛选、关联、解析失败、多个输入合并都不再说。
- 后果和提交后的提示:payload 不带 on_reject,从这次运行的图快照里按节点 id 读「未采用原流程时」;判为失败时写明采用盲算或都不对会终止运行、提示也照实说,缺省时不再挂那句,读不到时有条件地说、提示不下结论。
- 只有解析失败时和摘要阶段一样按兜底说(固定那句 + 解析的原话),默认展开对照;兜底的原话另有原因(比较超时)时附在下面,一边没有 SQL 时不说「两条 SQL 的写法不同」。
- 认不出任何指标时留一个「驳回并终止」(approved 为假),运行不再一直挂着。

时间线
- dual_check_catalog 的 item 是目录项的键(business_date 等),按数据目录的叫法写成「「orders」(shop)的业务日期」,认不出的键不显示。
- dual_check_limit 的 metric 是指标 ID,不再当名字加引号。
- challenge_skipped 的 no_report 是报告文档读不出来(报告节点找不到时节点直接报错),说法和下一步改成去查报告节点有没有执行成功、在不在执行到的分支上。

检查器
- 字段名和服务端校验报错的叫法(schema.py 的 DUAL_CHECK_FIELD_LABEL)对齐,处置选项以服务端的短说法开头;check-verify 在服务端合入后逐项比对。
- 盲算模型移出高级选项:时间线「模型相同」的定位要找得到它。
- 上游有几张口径卡时写明必须选(服务端校验会挡住发起运行),不再说「建议指定」。
- 「跟随设置」的当前值每次打开检查器都重取,改了设置回到画布不再是旧值。

测试
- 夹具里的差异说明换成 explain_sql_diff 对同一对 SQL 的真实输出,新增几对 SQL 的变体;backend/tests/test_dual_check_fixture.py 核对夹具和真实输出一致,并可重新生成。
- check-verify 补真实形状下的高亮、各种差异下「记入数据目录」说不说、只有解析失败和兜底原因、按处置说后果和提示、认不出指标时的驳回、叫法比对、多张口径卡、设置重取;check-decode 改用服务端真实的日志形状。check-verify 的耗时估计按实测改成 45 秒。
This commit is contained in:
ThearchyHelios
2026-10-05 16:10:55 +08:00
parent 8096c44626
commit 52baa0d65c
11 changed files with 914 additions and 181 deletions
+144 -13
View File
@@ -1,5 +1,5 @@
{
"_note": "双盲复算的预览用例和 scripts/check-verify.mjs 共用的夹具。表名、数字都是虚构的通用示例,不来自任何真实数据。",
"_note": "双盲复算的预览用例和 scripts/check-verify.mjs 共用的夹具。表名、数字都是虚构的通用示例,不来自任何真实数据。各处的 diff(差异说明)是服务端 explain_sql_diff 对同一对 SQL 的真实输出(方言 sqlite),由 backend/tests/test_dual_check_fixture.py 核对和重新生成,不要手改。variants 是另几对 SQL 及其差异说明,检查脚本拿来换掉「销售额」那个指标,看不同的差异下卡上怎么说",
"approval": {
"id": "ap-dc-0001",
"run_id": "run-dc-0001",
@@ -25,7 +25,7 @@
"blind_rendered": "51,388.3元",
"delta_pct": 12.5,
"diff": [
"原流程按支付时间 paid_at 筛选时间范围,盲算按下单时间 created_at 筛选"
"原流程按 paid_at 筛时间,盲算按 created_at"
],
"fallback": false
},
@@ -36,7 +36,9 @@
"original_rendered": "2.35%",
"blind_rendered": "3.10%",
"delta_pct": 31.91,
"diff": [],
"diff": [
"两条 SQL 的写法不同,未能归纳成具体差异,请对照原文"
],
"fallback": true
}
]
@@ -83,15 +85,13 @@
"items": [
{
"aspect": "time",
"text": "原流程按支付时间 paid_at 筛选时间范围,盲算按下单时间 created_at 筛选"
"text": "原流程按 paid_at 筛时间,盲算按 created_at"
}
],
"fallback": false,
"text_diff": [
"- WHERE paid_at >= '2026-09-01'",
"- AND paid_at < '2026-09-08'",
"+ WHERE created_at >= '2026-09-01'",
"+ AND created_at < '2026-09-08'"
"- orders.paid_at >= '2026-09-01' AND orders.paid_at < '2026-09-08'",
"+ orders.created_at >= '2026-09-01' AND orders.created_at < '2026-09-08'"
]
}
},
@@ -107,7 +107,7 @@
{
"path": "vars.kpi.refunds",
"value": 47,
"sql": "SELECT COUNT(*) AS refunds FROM refunds r JOIN orders o ON o.id = r.order_id WHERE o.status <> 'test'",
"sql": "SELECT COUNT(*) AS refunds\nFROM refunds r\nWHERE EXISTS (\n SELECT 1 FROM orders o\n WHERE o.id = r.order_id AND o.status <> 'test'\n)",
"source": "shop",
"alias": "Q2"
},
@@ -127,10 +127,10 @@
{
"path": "vars.kpi.refunds",
"value": 62,
"sql": "SELECT COUNT(DISTINCT order_id) AS refunds FROM refunds WHERE order_id IN (SELECT id FROM orders)",
"sql": "SELECT COUNT(*) AS refunds\nFROM refunds r\nWHERE r.order_id IN (SELECT id FROM orders)",
"source": "shop",
"alias": "B2",
"rationale": "退款笔数按有退款记录的订单去重计数"
"rationale": "退款笔数:订单表中能找到对应订单的退款记录数"
},
{
"path": "vars.kpi.orders",
@@ -152,8 +152,12 @@
],
"fallback": true,
"text_diff": [
"- SELECT COUNT(*) AS refunds FROM refunds AS r JOIN orders AS o ON o.id = r.order_id WHERE o.status <> 'test'",
"+ SELECT COUNT(DISTINCT order_id) AS refunds FROM refunds WHERE order_id IN (SELECT id FROM orders)"
"- EXISTS(",
"+ refunds.order_id IN (",
"- 1",
"+ \"orders@1\".id",
"- WHERE",
"- \"orders@1\".id = refunds.order_id AND \"orders@1\".status <> 'test'"
]
}
}
@@ -370,5 +374,132 @@
"timeout_s": 120
},
"daily_max_usd": 2.0
},
"variants": {
"time_range": {
"sql": [
"SELECT SUM(amount) AS gmv\nFROM orders\nWHERE paid_at >= '2026-09-01'\n AND paid_at < '2026-09-08'",
"SELECT SUM(amount) AS gmv\nFROM orders\nWHERE paid_at >= '2026-09-01'\n AND paid_at < '2026-09-09'"
],
"diff": {
"equivalent": false,
"items": [
{
"aspect": "time_range",
"text": "原流程的时间范围是 paid_at >= '2026-09-01' AND paid_at < '2026-09-08',盲算是 paid_at >= '2026-09-01' AND paid_at < '2026-09-09'"
}
],
"fallback": false,
"text_diff": [
"- orders.paid_at >= '2026-09-01' AND orders.paid_at < '2026-09-08'",
"+ orders.paid_at >= '2026-09-01' AND orders.paid_at < '2026-09-09'"
]
}
},
"filter_extra": {
"sql": [
"SELECT COUNT(*) AS orders\nFROM orders\nWHERE status <> 'test'",
"SELECT COUNT(*) AS orders\nFROM orders"
],
"diff": {
"equivalent": false,
"items": [
{
"aspect": "filter",
"text": "原流程排除了 status = 'test' 的行,盲算没有"
}
],
"fallback": false,
"text_diff": [
"- WHERE",
"- orders.status <> 'test'"
]
}
},
"two_filters": {
"sql": [
"SELECT COUNT(*) AS orders\nFROM orders\nWHERE channel = 'web'\n AND status <> 'refunded'",
"SELECT COUNT(*) AS orders\nFROM orders"
],
"diff": {
"equivalent": false,
"items": [
{
"aspect": "filter",
"text": "原流程只保留 channel = 'web' 的行,盲算没有这个条件"
},
{
"aspect": "filter",
"text": "原流程排除了 status = 'refunded' 的行,盲算没有"
}
],
"fallback": false,
"text_diff": [
"- WHERE",
"- orders.channel = 'web' AND orders.status <> 'refunded'"
]
}
},
"join": {
"sql": [
"SELECT COUNT(*) AS orders\nFROM orders o\nLEFT JOIN refunds r ON r.order_id = o.id",
"SELECT COUNT(*) AS orders\nFROM orders o\nJOIN refunds r ON r.order_id = o.id"
],
"diff": {
"equivalent": false,
"items": [
{
"aspect": "join",
"text": "原流程用 LEFT JOIN 关联 refunds 表,盲算用 INNER JOIN"
}
],
"fallback": false,
"text_diff": [
"- FROM orders AS orders",
"- LEFT JOIN refunds AS refunds",
"+ FROM orders AS orders, refunds AS refunds",
"+ WHERE",
"- ON orders.id = refunds.order_id",
"+ orders.id = refunds.order_id"
]
}
},
"dedup": {
"sql": [
"SELECT COUNT(DISTINCT user_id) AS buyers\nFROM orders",
"SELECT COUNT(user_id) AS buyers\nFROM orders"
],
"diff": {
"equivalent": false,
"items": [
{
"aspect": "aggregate",
"text": "原流程对 user_id 去重计数,盲算没去重"
}
],
"fallback": false,
"text_diff": [
"- COUNT(DISTINCT orders.user_id)",
"+ COUNT(orders.user_id)"
]
}
},
"parse": {
"sql": [
"SELECT SUM(amount) AS gmv\nFROM orders",
"SELEC SUM(amount) AS gmv\nFROM orders WHERE"
],
"diff": {
"equivalent": false,
"items": [
{
"aspect": "parse",
"text": "盲算:SQL 无法解析(第 1 行第 10 列附近),没有逐项比较"
}
],
"fallback": false,
"text_diff": []
}
}
}
}
+9 -2
View File
@@ -14,11 +14,13 @@ import data from './dual_check.json'
* - ?syn=dual-check-approval:正式运行里两路对不上的审批卡,宽栏(两条 SQL 左右并排)
* - ?syn=dual-check-approval-rail:同一张卡摆在 360px 的画布右栏里(两条 SQL 上下排)
* - ?syn=dual-check-approval-exploratory:探索运行,后果里不提出具
* - ?syn=dual-check-approval-empty:摘要里一个指标都没有(老服务端、写坏了的 payload),只能驳回
* - ?syn=dual-check-inspector:一张小画布(真的节点卡片)加 360px 的检查器,选中双盲复算节点;检查器改的是
* studio store 里的节点配置,卡片上的摘要跟着变
*
* 完整对照的工件(GET /api/artifacts/{id})、审批回复、设置、校验都由检查脚本用 page.route 伪造,直接打开时卡上照实说
* 无法加载完整对照。提交后 onResolved 只把运行 id 记到 window.__dualResolved,不去接事件流
* 完整对照的工件(GET /api/artifacts/{id})、这次运行的图快照(GET /api/runs/{id}/graph,卡上按它说节点的
* 「未采用原流程时」)、审批回复、设置、校验都由检查脚本用 page.route 伪造,直接打开时卡上照实说无法加载完整对照、
* 有条件地说后果。提交后 onResolved 只把运行 id 记到 window.__dualResolved,不去接事件流
*/
const approval = (patch: Partial<Approval> = {}): Approval => ({
...(data.approval as unknown as Approval),
@@ -78,5 +80,10 @@ export const cases: Record<string, () => JSX.Element> = {
<Card value={approval({ run_class: 'exploratory' })} />
</div>
),
'dual-check-approval-empty': () => (
<div className="mx-auto max-w-3xl p-4 text-sm" data-fixture="dual-check-approval-empty">
<Card value={approval({ payload: { ...data.approval.payload, summary: [] } })} />
</div>
),
'dual-check-inspector': () => <InspectorCase />,
}