Kamil Ogórek

Hey @alyssa-glean, thanks for the feedback. I do agree that the messaging here needs to be better, as right now, while technically correct, it doesn't provide much value. In the...

> In the meantime, is there a nice way for us to filter in/out issues in Sentry which encountered processing errors? Sorry, unfortunately not; https://docs.sentry.io/product/sentry-basics/search/searchable-properties/

@a-martynovich can you share a link to the event?

@alyssa-glean most of your frames are resolved correctly. The message from `cli` is correct, as the event is mapped, however your sourcemaps appear to be somehow malformed. Notice that most...

@a-martynovich @peter-catalin I can confirm that we had multiple issues with over-optimizations in the past. They are breaking produced sourcemaps, and there's nothing that we can do to resolve them...

@pulse00 if it's self-hosted, would it be maybe possible to provide just an event json file and the sourcemap file that was used for resolution? You can find both on...

```js import * as Sentry from "@sentry/browser"; const client = new Sentry.BrowserClient({ dsn: "%%dsn%%", release: '%%library_version%%', dist: '%%build_number%%', environment: process.env.NODE_ENV, integrations: [...Sentry.defaultIntegrations] }); const hub = new Sentry.Hub(client); // This...

> @kamilogorek, how can we currently prevent this call makeMain if we have multiple instances of Sentry running in the same application? Similar to this issue: #2783 There's no way...

> I would like to question whether "passing the error to error handling middleware (by calling `next` and passing the error )" is really the job of `Sentry.Handlers.requestHandler()`. Perhaps it...

> actually changes the behavior of Express How so? What is and what should be the behavior here?