diff --git a/backend-java/src/main/java/com/nanri/aiimage/modules/collectdata/service/CollectDataService.java b/backend-java/src/main/java/com/nanri/aiimage/modules/collectdata/service/CollectDataService.java index edc7d8694..1b8a8b26a 100644 --- a/backend-java/src/main/java/com/nanri/aiimage/modules/collectdata/service/CollectDataService.java +++ b/backend-java/src/main/java/com/nanri/aiimage/modules/collectdata/service/CollectDataService.java @@ -1156,10 +1156,12 @@ public class CollectDataService { } // 品牌查询失败的行不进结果、也不落无效品牌表(见上面 rejected/queryFailed 的区分), // 用户端因此完全没有出口:只在任务确实翻成成功时补一条通知。 + // 文案只写这一层观测得到的事实(未返回结果);真实原因(代理取不到 IP / 上游 503 / 被限流) + // 只有 BrandCheckClient 的 brand-check warn 日志知道,写进通知会把排查方向带偏。 if (updated > 0 && stats.brandQueryFailedCount > 0) { notificationDispatchService.pushPartialResult(task.getUserId(), task.getId(), MODULE_TYPE, task.getTaskNo(), stats.brandQueryFailedCount - + " 行商品的品牌检测未返回结果(品牌检测服务超时或被限流),这些行不计入结果条数," + + " 行商品的品牌检测未返回结果,这些行不计入结果条数," + "也没有被判定为无效品牌,可稍后单独重跑这些 ASIN"); } } finally { diff --git a/backend-java/src/test/java/com/nanri/aiimage/modules/collectdata/service/CollectDataPartialResultNoticeTest.java b/backend-java/src/test/java/com/nanri/aiimage/modules/collectdata/service/CollectDataPartialResultNoticeTest.java new file mode 100644 index 000000000..c32662e6a --- /dev/null +++ b/backend-java/src/test/java/com/nanri/aiimage/modules/collectdata/service/CollectDataPartialResultNoticeTest.java @@ -0,0 +1,149 @@ +package com.nanri.aiimage.modules.collectdata.service; + +import cn.hutool.core.io.FileUtil; +import com.baomidou.mybatisplus.core.MybatisConfiguration; +import com.baomidou.mybatisplus.core.metadata.TableInfoHelper; +import com.fasterxml.jackson.databind.ObjectMapper; +import com.nanri.aiimage.modules.notification.service.NotificationDispatchService; +import com.nanri.aiimage.modules.task.mapper.FileResultMapper; +import com.nanri.aiimage.modules.task.mapper.FileTaskMapper; +import com.nanri.aiimage.modules.task.model.entity.FileResultEntity; +import com.nanri.aiimage.modules.task.model.entity.FileTaskEntity; +import com.nanri.aiimage.modules.task.model.entity.TaskFileJobEntity; +import com.nanri.aiimage.modules.file.service.oss.OssStorageService; +import org.apache.ibatis.builder.MapperBuilderAssistant; +import org.junit.jupiter.api.AfterEach; +import org.junit.jupiter.api.BeforeAll; +import org.junit.jupiter.api.Test; +import org.junit.jupiter.api.extension.ExtendWith; +import org.mockito.ArgumentCaptor; +import org.mockito.InjectMocks; +import org.mockito.Mock; +import org.mockito.Spy; +import org.mockito.junit.jupiter.MockitoExtension; + +import java.io.File; + +import static org.assertj.core.api.Assertions.assertThat; +import static org.mockito.ArgumentMatchers.any; +import static org.mockito.ArgumentMatchers.anyLong; +import static org.mockito.ArgumentMatchers.anyString; +import static org.mockito.ArgumentMatchers.eq; +import static org.mockito.ArgumentMatchers.isNull; +import static org.mockito.Mockito.verify; +import static org.mockito.Mockito.when; + +/** + * 「任务成功但有一部分行没跑出来」通知文案(2026-10-02)。 + * + *
背景:后台通知里这条写死了「品牌检测服务超时或被限流」,而 10-02 取证出的真实根因是品牌链 + * 上游的采集代理取不到 IP(余额不足)与 503 —— 代码在这个位置只观测到「品牌检测没返回结果」, + * 观测不到原因。写死一个猜测的原因会把排查方向从代理/上游带到自身服务上。 + * + *
锁定契约:文案只陈述可观测事实(缺失行数、不计入结果条数、未判无效、可重跑),
+ * 不指认代码没有依据的具体故障原因;真实原因留在 BrandCheckClient 的 warn 日志里
+ * (brand-check 的 lastErr 字段),由运维按日志排查。
+ */
+@ExtendWith(MockitoExtension.class)
+class CollectDataPartialResultNoticeTest {
+
+ @Mock private FileTaskMapper fileTaskMapper;
+ @Mock private FileResultMapper fileResultMapper;
+ @Mock private CollectDataExcelAssemblyService excelAssemblyService;
+ @Mock private OssStorageService ossStorageService;
+ @Mock private NotificationDispatchService notificationDispatchService;
+
+ @Spy private ObjectMapper objectMapper = new ObjectMapper();
+
+ @InjectMocks private CollectDataService service;
+
+ private static final long TASK_ID = 29991L;
+
+ /** LambdaUpdateWrapper 需要实体的列缓存,纯单测里没有 Spring 容器要手工初始化。 */
+ @BeforeAll
+ static void initTableInfo() {
+ MapperBuilderAssistant assistant = new MapperBuilderAssistant(new MybatisConfiguration(), "");
+ TableInfoHelper.initTableInfo(assistant, FileTaskEntity.class);
+ TableInfoHelper.initTableInfo(assistant, FileResultEntity.class);
+ }
+
+ @AfterEach
+ void cleanWorkDir() {
+ FileUtil.del(new File(System.getProperty("java.io.tmpdir"), "collect-data-result/" + TASK_ID));
+ }
+
+ private FileTaskEntity taskWithQueryFailedRows(int queryFailedRows) {
+ FileTaskEntity task = new FileTaskEntity();
+ task.setId(TASK_ID);
+ task.setModuleType("COLLECT_DATA");
+ task.setStatus("RUNNING");
+ task.setTaskNo("CD-29991");
+ task.setUserId(7L);
+ task.setResultJson("{\"brandQueryFailedCount\":" + queryFailedRows + "}");
+ return task;
+ }
+
+ private TaskFileJobEntity job() {
+ TaskFileJobEntity job = new TaskFileJobEntity();
+ job.setTaskId(TASK_ID);
+ job.setResultId(5001L);
+ return job;
+ }
+
+ private FileResultEntity result() {
+ FileResultEntity result = new FileResultEntity();
+ result.setId(5001L);
+ result.setModuleType("COLLECT_DATA");
+ result.setSourceFilename("keywords.xlsx");
+ return result;
+ }
+
+ private String stubHappyPathAndCaptureDetail() {
+ when(fileTaskMapper.selectById(TASK_ID)).thenReturn(taskWithQueryFailedRows(7));
+ when(fileResultMapper.selectById(5001L)).thenReturn(result());
+ when(excelAssemblyService.writeWorkbookStreaming(any(), any(), any(), any())).thenReturn(12L);
+ when(ossStorageService.uploadResultFile(any(), anyString())).thenReturn("collect-data/29991.xlsx");
+ // 条件更新返回 1:任务翻成成功,这条「部分缺失」通知才会推给用户
+ when(fileTaskMapper.update(isNull(), any())).thenReturn(1);
+
+ service.processResultFileJob(job());
+
+ ArgumentCaptor