-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
feat(uptime-assertion-in-checks): Adding assertion_failure_data to the eap_converter #106833
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
base: master
Are you sure you want to change the base?
Conversation
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.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| attributes["status_reason_type"] = _anyvalue(status_reason["type"]) | ||
| attributes["status_reason_description"] = _anyvalue(status_reason["description"]) | ||
|
|
||
| assertion_failure_data = result["assertion_failure_data"] |
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.
I think that the bots are right and it'd be safer to use .get() here
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.
Oh sorry @wedamija, this was supposed to be a draft.
Ready for review now, pushed the rest of the changes, fixed the tests
Shoul let us query for the column from the eap trace_item table