From c5996d43ceee1333896f355a2c543d7b904ec213 Mon Sep 17 00:00:00 2001 From: Mimingguang Date: Tue, 11 Aug 2026 16:51:16 +0800 Subject: [PATCH] =?UTF-8?q?chore(changelog):=20=E6=8A=A2=E5=8D=95=E5=89=8D?= =?UTF-8?q?=E8=81=94=E7=B3=BB=E5=AF=B9=E6=96=B9=E5=8F=91=E4=B8=8D=E5=87=BA?= =?UTF-8?q?=E6=B6=88=E6=81=AF=20=E5=89=8D=E7=AB=AF=20implemented(9b824f5c)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...1_frontend_抢单前联系对方发不出消息-前端缺陷-管理后台.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/changelogs-v2/2026-08/11_frontend_抢单前联系对方发不出消息-前端缺陷-管理后台.md b/changelogs-v2/2026-08/11_frontend_抢单前联系对方发不出消息-前端缺陷-管理后台.md index e1b75b3..37c17f9 100644 --- a/changelogs-v2/2026-08/11_frontend_抢单前联系对方发不出消息-前端缺陷-管理后台.md +++ b/changelogs-v2/2026-08/11_frontend_抢单前联系对方发不出消息-前端缺陷-管理后台.md @@ -7,12 +7,12 @@ change_type: "前端缺陷" author: "wx(GIT)" backend_status: "not_required" gateway_status: "not_required" -frontend_status: "pending" +frontend_status: "implemented" frontend_owner: "mmg" -frontend_ref: "" +frontend_ref: "9b824f5c" target_release: "" verified_at: "" -status_note: "" +status_note: "前端已实现(9b824f5c)。changelog 怀疑的「peerAdminId=0 禁用发送」不成立:canSend/sendContent 门禁均不含 peerAdminId,open-house 对 '0' 传 '0' 后端返 200,emit 链全程无门禁。Workflow 对抗审查代码级证实真实根因——非抢单专属,是 request.js 通用缺陷:access token 过期(页面闲置首开聊天常见)时 open-house POST 首试在 shouldDedupe 写时间戳,后端业务体 401 → tryRefreshAndRetry 只清 signal/__requestKey 不清 writeRequestTimestamps,refresh 零延迟重放距首试 <300ms 被误判重复写、预 abort 抛 CanceledError,经 openFlow catch 的 isCanceledRequest 静默吞 → conversationKey 永不赋值,但标题因 peerName 空兜底仍显示「待接单房务」看似正常 → sendContent 因 key 空静默 return(=点发送无反应)。curl 持新鲜 token 不经 401 重放必 200,与观测吻合。修复:① request.js 两条重放路径(401 refresh 重放 + 5xx/限流重试)统一 config.dedupe=false(重放是合法重发非重复提交);② ChatDrawer open 失败(非主动取消)时 message.error 提示并关抽屉,不留死抽屉。测试:request.spec +2(修复前精确复现 CanceledError)37/37,ChatDrawer.spec +2 6/6,全量 190 文件 1780 用例全绿,checkpoint 含生产构建全过。" updated_at: "2026-08-11" base: "dev-v3" ---