Errors are unreadable in v9 and v10

[anthonator]

Environment

Elixir 1.14.5
Erlang 25.3.2.7
Sentry 10.1.0

Steps to Reproduce

Configured Sentry according to documentation on HexDocs.

Our config

if config_env() == :prod do
  config :sentry,
    dsn: System.fetch_env!("SENTRY_DSN"),
    enable_source_code_context: true,
    environment_name: System.fetch_env!("SENTRY_ENV"),
    hackney_opts: [
      ssl_options: [
        cacertfile: :certifi.cacertfile()
      ]
    ],
    root_source_code_paths: [File.cwd!()]
end

Expected Result

Errors would continue coming into Sentry in a readable format.

Actual Result

[whatyouhide]

Hi @anthonator, thanks for the report. I'd need a bit more info in order to debug this.

1. What's the error that you're seeing in the logs, that gets reported as the screenshot above?
2. Is your Sentry project configured as an Elixir project (on Sentry)?
3. Do you have a way to reproduce this with a minimal Elixir app?

[anthonator]

Thanks for getting back to me!

What's the error that you're seeing in the logs, that gets reported as the screenshot above?

2024-02-06 11:32:19.831** (exit) an exception was raised: | 2024-02-06 11:32:19.831 | ** (exit) an exception was raised: |  
-- | -- | -- | --
2024-02-06 11:32:19.831 | ** (exit) an exception was raised: |  

2024-02-06 11:32:19.831    ** (Ecto.ConstraintError) constraint error when attempting to insert struct: |   |   | 2024-02-06 11:32:19.831 | ** (Ecto.ConstraintError) constraint error when attempting to insert struct: |  
  |   | 2024-02-06 11:32:19.831 | ** (Ecto.ConstraintError) constraint error when attempting to insert struct: |  
2024-02-06 11:32:19.8312024-02-06 11:32:19.831    * "***_index" (unique_constraint)2024-02-06 11:32:19.8312024-02-06 11:32:19.831If you would like to stop this constraint violation from raising an2024-02-06 11:32:19.831exception and instead add it as an error to your changeset, please2024-02-06 11:32:19.831call `unique_constraint/3` on your changeset with the constraint2024-02-06 11:32:19.831`:name` as an option.2024-02-06 11:32:19.8312024-02-06 11:32:19.831The changeset defined the following constraints:2024-02-06 11:32:19.8312024-02-06 11:32:19.831    * "***_index" (unique_constraint)2024-02-06 11:32:19.8312024-02-06 11:32:19.831        (ecto 3.10.3) lib/ecto/repo/schema.ex:804: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/32024-02-06 11:32:19.831        (elixir 1.14.5) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/22024-02-06 11:32:19.831        (ecto 3.10.3) lib/ecto/repo/schema.ex:788: Ecto.Repo.Schema.constraints_to_errors/32024-02-06 11:32:19.831        (ecto 3.10.3) lib/ecto/repo/schema.ex:769: Ecto.Repo.Schema.apply/42024-02-06 11:32:19.831        (ecto 3.10.3) lib/ecto/repo/schema.ex:377: anonymous fn/15 in Ecto.Repo.Schema.do_insert/42024-02-06 11:32:19.831        (ecto 3.10.3) lib/ecto/multi.ex:844: Ecto.Multi.apply_operation/52024-02-06 11:32:19.831        (elixir 1.14.5) lib/enum.ex:2468: Enum."-reduce/3-lists^foldl/2-0-"/32024-02-06 11:32:19.831        (ecto 3.10.3) lib/ecto/multi.ex:818: anonymous fn/5 in Ecto.Multi.apply_operations/5 |   |   | 2024-02-06 11:32:19.831 |   |   |   |   | 2024-02-06 11:32:19.831 | * "***_index" (unique_constraint) |   |   |   | 2024-02-06 11:32:19.831 |   |   |   |   | 2024-02-06 11:32:19.831 | If you would like to stop this constraint violation from raising an |   |   |   | 2024-02-06 11:32:19.831 | exception and instead add it as an error to your changeset, please |   |   |   | 2024-02-06 11:32:19.831 | call `unique_constraint/3` on your changeset with the constraint |   |   |   | 2024-02-06 11:32:19.831 | `:name` as an option. |   |   |   | 2024-02-06 11:32:19.831 |   |   |   |   | 2024-02-06 11:32:19.831 | The changeset defined the following constraints: |   |   |   | 2024-02-06 11:32:19.831 |   |   |   |   | 2024-02-06 11:32:19.831 | * "***_index" (unique_constraint) |   |   |   | 2024-02-06 11:32:19.831 |   |   |   |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:804: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/3 |   |   |   | 2024-02-06 11:32:19.831 | (elixir 1.14.5) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2 |   |   |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:788: Ecto.Repo.Schema.constraints_to_errors/3 |   |   |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:769: Ecto.Repo.Schema.apply/4 |   |   |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:377: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4 |   |   |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/multi.ex:844: Ecto.Multi.apply_operation/5 |   |   |   | 2024-02-06 11:32:19.831 | (elixir 1.14.5) lib/enum.ex:2468: Enum."-reduce/3-lists^foldl/2-0-"/3 |   |   |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/multi.ex:818: anonymous fn/5 in Ecto.Multi.apply_operations/5
  |   | 2024-02-06 11:32:19.831 |   |  
  |   | 2024-02-06 11:32:19.831 | * "***_index" (unique_constraint) |  
  |   | 2024-02-06 11:32:19.831 |   |  
  |   | 2024-02-06 11:32:19.831 | If you would like to stop this constraint violation from raising an |  
  |   | 2024-02-06 11:32:19.831 | exception and instead add it as an error to your changeset, please |  
  |   | 2024-02-06 11:32:19.831 | call `unique_constraint/3` on your changeset with the constraint |  
  |   | 2024-02-06 11:32:19.831 | `:name` as an option. |  
  |   | 2024-02-06 11:32:19.831 |   |  
  |   | 2024-02-06 11:32:19.831 | The changeset defined the following constraints: |  
  |   | 2024-02-06 11:32:19.831 |   |  
  |   | 2024-02-06 11:32:19.831 | * "***_index" (unique_constraint) |  
  |   | 2024-02-06 11:32:19.831 |   |  
  |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:804: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/3 |  
  |   | 2024-02-06 11:32:19.831 | (elixir 1.14.5) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2 |  
  |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:788: Ecto.Repo.Schema.constraints_to_errors/3 |  
  |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:769: Ecto.Repo.Schema.apply/4 |  
  |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/repo/schema.ex:377: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4 |  
  |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/multi.ex:844: Ecto.Multi.apply_operation/5 |  
  |   | 2024-02-06 11:32:19.831 | (elixir 1.14.5) lib/enum.ex:2468: Enum."-reduce/3-lists^foldl/2-0-"/3 |  
  |   | 2024-02-06 11:32:19.831 | (ecto 3.10.3) lib/ecto/multi.ex:818: anonymous fn/5 in Ecto.Multi.apply_operations/5

Is your Sentry project configured as an Elixir project (on Sentry)?

No, it is not. Although this hasn't been an issue for projects using v8.

Do you have a way to reproduce this with a minimal Elixir app?

No, not currently

[whatyouhide]

No, it is not. Although this hasn't been an issue for projects using v8.

If you change the project type to Elixir, does that change anything?

No, not currently

It's really hard for me to help debug this without any way to reproduce it 😢. All my tests point to errors showing up correctly, and we're on 10.1.0 at work and errors also show up correctly (also with Cowboy + Phoenix).

[anthonator]

I recently upgraded another project to v10.1.0 and we're seeing the same issue. The Sentry project for this application is set as Elixir. Everything worked perfectly using v8.x.

If I have time I'll try to put together a minimal reproduction app.

Here are some additional details.

This is the first line of start/2 in our Application module:

:logger.add_handler(:sentry_handler, Sentry.LoggerHandler, %{})

We also removed all use of Sentry.LoggerBackend.

This is the first line of our endpont:

use Sentry.PlugCapture

The runtime.exs looks like this.

if config_env() == :prod do
  config :sentry,
    dsn: System.get_env("SENTRY_DSN"),
    enable_source_code_context: true,
    environment_name: System.get_env("SENTRY_ENV"),
    hackney_opts: [
      ssl_options: [
        cacertfile: :certifi.cacertfile(),
        customize_hostname_check: [match_fun: :public_key.pkix_verify_hostname_match_fun(:https)],
        verify: :verify_peer,
        verify_fun: &:ssl_verify_hostname.verify_fun/3,
        versions: [:"tlsv1.2", :"tlsv1.3"]
      ]
    ],
    root_source_code_paths: [File.cwd!()]
end

This is how we create the release in our Dockerfile:

RUN apk upgrade --no-cache \
    && mix deps.get \
    && mix compile \
    && mix app.config \
    && mix sentry.package_source_code \
    && mix release

Here's another example of what we're seeing in Sentry.