JUnit and request recorders both record the same integration test; no way to pick one
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- java, spring-boot
调研方向
Start by reproducing with mvn -Dtest=PetClinicIntegrationTests#testOwnerDetails test in spring-petclinic, then compare the outputs under tmp/appmap/junit and tmp/appmap/request_recording. The issue leaves open whether the fix is a configuration switch or a documented rule, so a maintainer decision is needed first. Done means one recorder is chosen when both would fire, with the rule or setting documented.
由索引模型根据 Issue 内容生成。
描述
Summary
A single Spring Boot integration test that issues an HTTP request through a real port produces two recordings of the same behavior: one from the JUnit recorder, one from the request recorder. Both recorders are on by default, neither knows about the other, and there is no documented setting to disable one.
Agent 1.30.1, spring-petclinic @ b26f235.
Repro
mvn -Dtest=PetClinicIntegrationTests#testOwnerDetails test
ls tmp/appmap/junit tmp/appmap/request_recording
Observed
tmp/appmap/junit/org_..._PetClinicIntegrationTests_testOwnerDetails.appmap.json
tmp/appmap/request_recording/1789755390_129__owners_1.appmap.json
The JUnit recording contains the test method and everything under it; the request one contains the request, controller and SQL. They overlap almost entirely. The request recording's filename embeds a timestamp and a port-dependent counter, so it differs on every run and cannot serve as a stable baseline identity (the gold-traces engine's discover returns both and leaves the choice open).
Expected
A setting to select which recorder runs when both would fire (e.g. suppress request recordings that occur inside an active JUnit recording), or at least document the rule: curate the JUnit recording, use a request recording only when no test drives the endpoint.
- 主要语言
- Java
- 星标
- 88
- 派生
- 17
- 平均合并
- 2 天 2 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
getappmap/appmap-java 的其他 Issue
-
appmap.yml packages path matching zero classes yields a healthy-looking recording with no warning未关闭
难度 3/5 1-2 天 新手友好度 45/100
getappmap/appmap-java#332 · 1 条评论 ·
-
Git metadata dropped in a git worktree (.git file with gitdir: pointer not followed)可能已有人在做 @dividedmind 于 2 天前认领。 未关闭
getappmap/appmap-java#331 · 1 条评论 · 已指派 1 人 ·
-
Labeled methods should always be recorded, even if they match trivial-method filters可能已有人在做 @kgilpin 于 192 天前认领。 未关闭
getappmap/appmap-java#323 · 1 个 reaction · 已指派 2 人 ·
-
难度 3/5 1-2 天 新手友好度 35/100
getappmap/appmap-java#322 ·
-
难度 5/5 一周以上 新手友好度 35/100
getappmap/appmap-java#308 ·
查看 getappmap/appmap-java 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
objectionary/eo-graphs#80 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
objectionary/jucs#141 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 88/100
repowise-dev/repowise#3335 ·
维护者通常 1 天内回复