getsentry / getsentry/sentry-java
Pure tombstone events duplication
- 主要語言
- Kotlin
- 星號
- 1.4k
- 分支
- 478
- 平均合併
- 3 天 4 小時
- 30 天內合併 PR
- 72
描述
### Integration
sentry-android
### Build System
Gradle
### AGP Version
8.14.0
### Proguard
Enabled
### Other Error Monitoring Solution
No
### Version
8.44.1
### Steps to Reproduce
Unfortunately, I was unable to reproduce this problem on local devices.
### Expected Result
Tombstone events are not duplicated.
### Actual Result
I see duplicate events in the reports received from users:
I downloaded two event's jsons and compared:
```
E:\work\tmp>diff "l.txt" "r.txt"
2c2
< "event_id": "b4a16e59fd854caaa8ebae2ea2828dd0",
---
> "event_id": "5716230e7f254ec9b3bcfe13d562bde2",
6893,6894c6893,6894
< "nodestore_insert": 1788397282.7622,
< "received": 1788397276.54076,
---
> "nodestore_insert": 1788358349.59206,
> "received": 1788358346.52165,
```
All content is identical, except from id and received time.
Therefore, I assume there is a bug when same tombstone may be reported twice.
P.S. Ignore the fact that the "Release" field is missing from the events - that's another issue I started to address, but noticed duplicates. For some reason, pure tombstone events don't have custom tags, breadcrumbs and attachment. If someone knows the reason, please advice, any hints are highly appreciated.
貢獻指南
研究方向
從 sentry-android 的 tombstone 回報路徑開始,比較提供的兩個事件 JSON,著重探究為什麼相同的內容會被接收兩次。如果可能,重現所回報的 Android 和 Gradle 設定;當單一 tombstone 只產生一個事件,且重複事件行為由適當的測試涵蓋時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- android, java, kotlin
- 領域
- mobile-dev
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 活躍
- 描述清晰度
- 需要釐清
- 新手友好度
- 38/100