getsentry / getsentry/sentry-javascript

Unrelated errors are grouped together

Abierto
#16,409 11 comentarios 0 reacciones 0 asignados Ver en GitHub
Core Improvement
Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
1.8k
Merge medio
1 d 17 h
PR fusionados (30 d)
515

Descripción

### Is there an existing issue for this?

- [x] I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- [x] I have reviewed the documentation https://docs.sentry.io/
- [x] I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

### How do you use Sentry?

Sentry Saas (sentry.io)

### Which SDK are you using?

@sentry/nextjs

### SDK Version

9.x

### Framework Version

Next 15.3.2, TRPC 11.1

### Link to Sentry event

_No response_

### Reproduction Example/SDK Setup

I upgraded from version 7 to version 9, and after the upgrade a lot of my errors are grouped together even though they are not related except they all are "TRPCError"s.

### Steps to Reproduce

Triggering an error in different trpc procedures.

### Expected Result

Triggering an error from different procedures should result in a separate issue per error.

### Actual Result

Errors ends up in the same issue on Sentry with the title and message from the initial error shown on top.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.