getsentry / getsentry/sentry-java
Align callback error handling with other SDKs
- 主要言語
- Kotlin
- スター
- 1.4k
- フォーク
- 478
- 平均マージ
- 2日 23時間
- マージ済み PR(30日)
- 67
説明
### Description
Currently Java SDK does not follow the [new spec for callbacks](https://github.com/getsentry/sentry-docs/pull/19189).
If an error happens in a customer callback (hook), the SDK should fall back according to spec.
Gaps in Java SDK:
- `beforeBreadcrumb`: on error the breadcrumb is added as is, it should be dropped instead
- `eventProcessor`: on error the event/telemetry goes further in the pipeline, it should be dropped instead
Client reports:
- there's a new discard reason `callback_error ` (https://develop.sentry.dev/sdk/telemetry/client-reports/#discard-reasons-1) which should be used to make this distinguishable from things being filtered out on purpose.
コントリビューションガイド
調査の方向性
Start by tracing the Java SDK handling for the beforeBreadcrumb and eventProcessor callbacks, then inspect how client-report discard reasons are represented. The work is complete when callback errors drop the breadcrumb or event and record the callback_error discard reason, matching the referenced callback specification.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- java
- 領域
- tooling
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 66/100