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

Informative error messages related to pgtrigger #2935

Open
3 tasks
Sepehr-Sobhani opened this issue Feb 28, 2025 · 3 comments
Open
3 tasks

Informative error messages related to pgtrigger #2935

Sepehr-Sobhani opened this issue Feb 28, 2025 · 3 comments

Comments

@Sepehr-Sobhani
Copy link
Contributor

Description of the Tech Debt

Currently, all error messages related to server issues are displayed as Internal Server Error on the frontend; however, we should make this more informative for errors associated with pgtriggers. We must find a way to distinguish pgtrigger error messages from other errors and reflect this in the handle_exception function.

Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level Value
High
3
Medium
2
Low
1
Technical Debt - Risk Types Level Value
Business Area Risk - Risk of business area visibility / damage to user experience 0 0
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it 0 0
System Fault Risk - Risk of system errors or application downtime 0 0
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time? 0 0
Time Sink Risk - How much will this tech debt slow the development process down 0 0
TOTAL SCORE:
0 0

Development Checklist:

  • Checklist item
  • Checklist item
  • Checklist item
@pbastia
Copy link
Contributor

pbastia commented Feb 28, 2025

@patriciarussellCAS this is medium-low priority, not necessary for MVP

@patriciarussellCAS
Copy link

Is this related or similar to the reporting ticket # 597? tagging @fviduya for visibility.

@Sepehr-Sobhani
Copy link
Contributor Author

Is this related or similar to the reporting ticket # 597? tagging @fviduya for visibility.

I think they are similar, but we're dealing with two different types of errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants