Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

["Request"] better stack traces when tracing withError #3351

Open
kyay10 opened this issue Jan 18, 2024 · 0 comments · May be fixed by #3358
Open

["Request"] better stack traces when tracing withError #3351

kyay10 opened this issue Jan 18, 2024 · 0 comments · May be fixed by #3358
Assignees

Comments

@kyay10
Copy link
Collaborator

kyay10 commented Jan 18, 2024

When using traced with withError inside, the stacktrace will always point at the withError lambda, and won't include any information about where the error occurred originally. Adding some way to attach that extra information would be helpful so that the traces reflect the original error location

@kyay10 kyay10 self-assigned this Jan 23, 2024
@kyay10 kyay10 linked a pull request Jan 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant