-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
chore(jira): Add more logs/expose them better #92359
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
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## master #92359 +/- ##
========================================
Coverage 87.91% 87.92%
========================================
Files 10217 10220 +3
Lines 585519 585678 +159
Branches 22720 22720
========================================
+ Hits 514782 514933 +151
- Misses 70309 70317 +8
Partials 428 428 |
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.
lgtm, thank you for adding to the extras!
}, | ||
) | ||
return | ||
raise IntegrationFormError({"email": "Unable to find the requested user"}) |
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.
IntegrationFormError
is generally for misconfigured ticket/sentry app forms. is there a more relevant type of error we can raise?
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.
From the existing exceptions I see we have we could do IntegrationInstallationConfigurationError
since this usually means the user either isnt verified or put a bad email/jira user.
I can narrow down the error message to be more helpful though if the user isn;t verified on sentry's side.
It was harder to debug the jira assignment sync issue because we swallowed the errors
This could negatively affect our SLOs but I'd rather see all the errors first and then narrow from there,