-
Notifications
You must be signed in to change notification settings - Fork 31
Set get frames public #41
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
Conversation
@PeterIvanov
PeterIvanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR requires a description.
The first thing to know here is a use case. I'm fairly sure that it's better to provide utilities for it, if it's a valid case, rather than exposing some internals from errorx.
PeterIvanov
commented
Jul 11, 2023
Maybe we adopt this exact use case?
Instead of API focused on just exposing stack frames, make an api for conversion. This would highlight that you don't need to extract this information as-is, but if you need to feed it to some system with custom stack frames format, you can.
Such conversion API can also be based on interface for errorx frame, not the actual representation, as an added bonus.
What's your view on such idea?
@PeterIvanov
PeterIvanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pending an answer to the question above, marking this PR as Request changes for now.
reaganiwadha
commented
Jan 15, 2024
For monitoring tools like github.com/getsentry/sentry-go, it's important to expose the callstack so the error can be traced.
This is how Sentry extracts stack trace from other error libraries. While I don't think errorx should necessarily adhere to the way Sentry parses stack trace, an exposed API to get the frames from the Error should be available for custom stack trace parsing.
reaganiwadha
commented
Jan 15, 2024
Instead of API focused on just exposing stack frames, make an api for conversion. This would highlight that you don't need to extract this information as-is, but if you need to feed it to some system with custom stack frames format, you can.
Im not sure how a conversion API for call stack works, can you provide an example?
PeterIvanov
commented
Jan 16, 2024
As far as I can recall, the idea was that we add an API like this:
func (e *Error) ExportStackFrames(originalFrames []FrameInterface) any
This way, we:
- Hint that extracting stack frames is not an intended high-level API for dealing with errors
- Hide behind the interface to avoid, say, marshalling issues
PeterIvanov
commented
Jan 16, 2024
In this PR, the second point is already addressed, so I'm generally OK with that. Just asked for an opinion on an idea.
Uh oh!
There was an error while loading. Please reload this page.
In our applications, we catch all errors in our webservices and our batches and create sentry issues with the errorx stacktrace.