fix(guardrails): 京东上架五守卫格整量补记(24272a91 点名 87 例没跑整量、两处账本与四个分母漏记,2026-11-18 发版前整量 5689 例抓到)——①TaskFailureCategoryGuardrail B51-R1:JdPublishIngestService.summarizeTerminal 文案先落局部变量 message 再配对写列(原来三元里各写各的表达式被「写的列与文案不是同一个来源」判红;CollectDataService failTask 正本形状同源);②ApiGuardCoverageAuditor PENDING_CONVERGENCE 登记 /api/jd-publish(与 /api/jd-collect 逐形状同族:建单等五端点 requireOwnershipUserId fail-closed、chunk 判死口凭据化 isTrustedInternalToken 匿名拒绝判死、JdPublishChunkRequest 不带 userId 不进身份扫描);③RequestSuppliedIdentityOutletTest 写类分母 133→136(建单 DTO 形+activate+heartbeat 三支)、读类 67→69(items+progress 两支),chunk 不计入(留痕注释);④MigratedSqlEquivalenceTest XML_SELECT_TOTAL 103→105+NOT_MIGRATED 点名 JdPublishItemMapper#selectPublishableItems/countByPublishStatus;⑤SqlLayeringConventionTest XML_STATEMENT_TOTAL 147→149。判据:点名 5 类 34/34 绿+整量 5689 例(0 失败/19 skip)BUILD SUCCESS 9:51min——修复 jar 与平台隔离 jar 同窗
This commit is contained in:
@@ -118,6 +118,11 @@ public class ApiGuardCoverageAuditor implements SmartInitializingSingleton {
|
||||
* requireOwnershipUserId(fail-closed 401),chunk 与 heartbeat 和 collect-data/delete-brand
|
||||
* 同形状(本机桌面执行器不带凭据,行归属以任务 owner 投影);chunk 的 error 上报已接整单
|
||||
* 判死,其 owner 对撞收口随 v1.4 Phase 6.1 落,判死口凭据化后随统一批进名单</li>
|
||||
* <li>{@code /api/jd-publish} —— v1.5 京东商品上架任务面(建单/activate/items/progress/chunk/
|
||||
* heartbeat):与 /api/jd-collect 逐形状同族——建单等五端点方法体已有 requireOwnershipUserId
|
||||
* (fail-closed 401,B98-07 同形债预防),chunk 判死口凭据化(isTrustedInternalToken,
|
||||
* 匿名一律拒绝判死),行级落库与 jd-collect 同形状(本机桌面执行器不带凭据,行归属以
|
||||
* 任务 owner 投影);判死口凭据化后随统一批进名单</li>
|
||||
* </ul>
|
||||
*/
|
||||
static final Set<String> PENDING_CONVERGENCE = Set.of(
|
||||
@@ -127,7 +132,8 @@ public class ApiGuardCoverageAuditor implements SmartInitializingSingleton {
|
||||
"/api/delete-brand",
|
||||
"/api/module-templates",
|
||||
"/api/split",
|
||||
"/api/jd-collect");
|
||||
"/api/jd-collect",
|
||||
"/api/jd-publish");
|
||||
|
||||
private final RequestMappingHandlerMapping handlerMapping;
|
||||
|
||||
|
||||
+5
-2
@@ -170,6 +170,9 @@ public class JdPublishIngestService {
|
||||
reason.append(",未发布 ").append(unpublished).append(" 行");
|
||||
}
|
||||
LocalDateTime now = LocalDateTime.now();
|
||||
// 文案先落局部变量再配对写列(B51-R1 守卫「写的列与文案同一个来源」:列由同一句文案派生,
|
||||
// 三元里各写各的表达式会被 TaskFailureCategoryGuardrailTest 判为不同源即红)。
|
||||
String message = anyFailed ? reason.toString() : null;
|
||||
int updated = fileTaskMapper.update(null, new LambdaUpdateWrapper<FileTaskEntity>()
|
||||
.eq(FileTaskEntity::getId, taskId)
|
||||
.eq(FileTaskEntity::getModuleType, JdPublishTaskService.MODULE_TYPE)
|
||||
@@ -177,8 +180,8 @@ public class JdPublishIngestService {
|
||||
.set(FileTaskEntity::getStatus, status)
|
||||
.set(FileTaskEntity::getSuccessFileCount, success)
|
||||
.set(FileTaskEntity::getFailedFileCount, failed)
|
||||
.set(FileTaskEntity::getErrorMessage, anyFailed ? reason.toString() : null)
|
||||
.set(FileTaskEntity::getFailureCategory, anyFailed ? TaskFailureLedger.categoryOf(reason.toString()) : null)
|
||||
.set(FileTaskEntity::getErrorMessage, message)
|
||||
.set(FileTaskEntity::getFailureCategory, message == null ? null : TaskFailureLedger.categoryOf(message))
|
||||
.set(FileTaskEntity::getUpdatedAt, now)
|
||||
.set(FileTaskEntity::getFinishedAt, now));
|
||||
if (updated > 0) {
|
||||
|
||||
Reference in New Issue
Block a user