Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.51%. Comparing base (703e4af) to head (09f5af9).
Report is 1068 commits behind head on master.

@@            Coverage Diff             @@
##           master    #1231      +/-   ##
==========================================
+ Coverage   97.92%   98.51%   +0.59%     
==========================================
  Files         193       98      -95     
  Lines        8280     4450    -3830     
==========================================
- Hits         8108     4384    -3724     
+ Misses        172       66     -106     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@st0012 we just ran into an issue that I believe was caused by this. Serializing the hint causes the exception object to no longer be accessible to the async block, as it's been converted to JSON. We have a (temporary) check in our async block that needs to actually inspect the Exception#backtrace, and it's no longer accessible via hint[:exception] (which is what it was pre-JSON serialization).

I understand wanting to provide a serialized value that can be easily passed to SendEventJob (or some other custom Active Job-like class), so I'm wondering if there's another way for those who need to access the exception itself to do so?

you can access the backtrace through the event payload like:

    if hint["exception"]
      exception = event["exception"]["values"].first
      stacktrace = exception["stacktrace"]["frames"]
      # which looks like this
      #
      # [
      #   {:project_root=>"/Users/st0012/projects/sentry-ruby/sentry-ruby", :abs_path=>"/some/other/path", :function=>"other_function", :lineno=>1412, :in_app=>false, :filename=>"/some/other/path"},
      #   {:project_root=>"/Users/st0012/projects/sentry-ruby/sentry-ruby", :abs_path=>"/path/to/some/file", :function=>"function_name", :lineno=>22, :in_app=>false, :filename=>"/path/to/some/file"}
      # ]
    end