Retrying within rescue will chain errors and fail to send to Sentry
維護者通常 2 天內回覆
@sl0thentr0py 已經在處理了。
開始於 2022年11月21日。
評估
這個 Issue 還沒有評估資料。
描述
Issue Description
I have a method that will try to perform an operation, and if it fails it will attempt it again within the rescue block, up to 20 times, then raises an exception.
What ends up happening is that sentry will end up capturing the chain of 20 exceptions, and each exception will include the entire stack trace when it happened, so it will generate an enormous stack trace. The SDK will then try to crop the stack trace, but fail because while cutting each exception down to 250 frames, we are still left with a total of over 1000 frames and the envelope will be too large to send.
Reproduction Steps
class Chainer
def chain_errors(n=20)
raise StandardError.new("Been launched #{n} times")
rescue StandardError => e
if n == 0
Sentry.capture_exception(e)
else
chain_errors(n - 1)
end
end
end
Then I launch a ruby console and call Chainer.new.chain_errors, which fails and Chainer.new.chain_errors 2, which succeeds
Expected Behavior
I would expect Sentry to perform some sort of logging, either by removing most of the exceptions or by cropping all stack traces further so the error would end up on sentry (maybe this could be a setting). I would also expect that, if that fails, it would throw an error that explains the problem better
Actual Behavior
Sentry will give up after removing the breadcrumbs and cropping the stack traces, and throw a message without much information on the error into the rails logs:
Envelope item [event] is still oversized after size reduction: {event_id: 34, level: 7, timestamp: 22, release: 48, environment: 12, server_name: 14, modules: 11411, message: 2, user: 2, tags: 52, contexts: 993, extra: 2, fingerprint: 2, transaction: 52, transaction_info: 17, platform: 6, sdk: 40, type: 7, threads: 94, exception: 283677}
Ruby Version
2.7.5
SDK Version
5.5.0
Integration and Its Version
No response
Sentry Config
No response
- 主要語言
- Ruby
- 星號
- 990
- 分支
- 552
- 平均合併
- 2 天 16 小時
- 30 天內合併 PR
- 29
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
getsentry/sentry-ruby 的其他 Issue
-
Bug Ruby
難度 2/5 1-3 小時 新手友好度 76/100
getsentry/sentry-ruby#3211 · 1 則留言 ·
維護者通常 2 天內回覆
-
Events dropped client-side for size are only logged at debug level and not recorded as lost可能已有人在做 @sentry-junior 今天認領。 未關閉Bug Junior: repro Ruby
難度 2/5 1-3 小時 新手友好度 76/100
getsentry/sentry-ruby#3209 · 2 則留言 · 1 個 reaction ·
維護者通常 2 天內回覆
-
with_child_span drops spans when blocks exit via break, return, or throw可能已有人在做 @itsrayeedscodespace 於 1 天前認領。 未關閉Bug Ruby Traces Waiting for: Product Owner
難度 2/5 1-3 小時 新手友好度 38/100
getsentry/sentry-ruby#3206 · 1 則留言 ·
維護者通常 2 天內回覆
-
Let apps choose how the client IP on events is determined可能已有人在做 @sl0thentr0py 於 11 天前認領。 未關閉Improvement Ruby
getsentry/sentry-ruby#3180 · 2 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 2 天內回覆
-
breaking change Next Major
難度 2/5 1-3 小時 新手友好度 58/100
getsentry/sentry-ruby#3176 · 1 則留言 ·
維護者通常 2 天內回覆
查看 getsentry/sentry-ruby 的全部 Issue
相似的 Issue
-
enhancement
難度 2/5 1-3 小時 新手友好度 66/100
internetee/registry#2984 ·
維護者通常 6 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
ecosyste-ms/issues#862 ·
維護者通常 1 天內回覆
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configured可能已有人在做 @mimosa 今天認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
riscv/riscv-unified-db#2829 ·
維護者通常 1 天內回覆
-
⛓️ Security Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
難度 2/5 1-3 小時 新手友好度 82/100
rubyforgood/casa#7404 ·
維護者通常 1 天內回覆