-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add error tracking to TRACKER with new EventKind #450
Comments
/bounty $25 |
💎 $25 bounty • Tailcall Inc.Steps to solve:
🙏 Thank you for contributing to antinomyhq/forge!
|
/attempt #450
|
@tusharmath for ease of testing, do you have any input examples that consistently cause errors? |
Use a dumber smaller model, u will get issues eventually. |
💡 @onyedikachi-david submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Problem
The application currently lacks a mechanism to track errors that occur during runtime. This limits our ability to monitor application health and proactively address issues users are encountering.
Proposed Solution
Extend the
EventKind
enum to include anErrorOccurred
variant that can capture:Benefits
This enhancement would allow us to:
Implementation Details
ErrorOccurred(ErrorDetails)
variant toEventKind
enumErrorDetails
struct to contain error informationname()
andvalue()
methods to handle the new variantAcceptance Criteria
ErrorOccurred
variant added toEventKind
Note
This change should maintain the current opt-out behavior for tracking, ensuring users who have disabled tracking don't have their errors tracked either.
The text was updated successfully, but these errors were encountered: