Dev: ASA N+1 Query
Open
4Refinement
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
Sentry Issue: [BACKEND-5E](https://bcps-wps.sentry.io/issues/6642365232/?referrer=github_integration)
| | |
| ------------- | --------------- |
| **Offending Spans** | db - SELECT critical_hours.start_hour, critical...
Contributor guide
Research direction
Start with the linked Sentry issue and its offending database span, then trace the ASA path that issues the SELECT against critical_hours. Done means the N+1 query behavior is addressed and the resulting query activity is verified against the reported Sentry issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100