Andrea Leopardi

If you don't include args you might get errors related to very different calls fingerprinted and grouped together. I personally think we should lean on too many errors rather than...

Yes, a frame-based API is possible because the Rust crate we're using in nimble_lz4 supports it: https://docs.rs/lz4_flex/latest/lz4_flex/#example-compress-data-on-stdin-with-frame-format Would you be willing to cook up a PR? 🙃

This doesn't affect "normal" use cases where the range is much smaller, right? (Given the issue only appears with large numbers)

I cleaned up the error, it's here in case it makes it easier to debug: ```elixir [ [ initial_call: {:cowboy_stream_h, :request_process, [:Argument__1, :Argument__2, :Argument__3]}, pid: %PID{}, registered_name: [], error_info: {:exit,...

I’m a little stumped by this to be honest. I don't see cowboy logging anything on its own in `cowboy_stream_h.erl`, which could explain this log being reported. In any case,...

You can filter them out yourself in your `before_send`, by matching on parts of the message. I don't think it's a good idea to filter them out in Sentry before...

For others on this, I was able to reproduce this by: 1. Cloning https://github.com/tommasop/elixir-boilerplate 2. Move the `config :sentry` from `config/runtime.exs` to `config/config.exs` 3. Put in your actual Sentry DSN...

I get this error with `/api/login` because `AppName.VerifyAdminRequest` checks for a bad function clause (`path_info: ["api/login" | _]`).  Fixing it to be `path_info: ["api", "login" | _]` raises the...

@kaiserdan yes would love the help. Does the HTTP/2 spec say what to do in case of unknown errors?

Yeah I would like something like `{:custom_error, code}`. Thoughts? You're welcome to start on a PR and we can continue the discussion there 🙃