learningequality / learningequality/studio
Prevent Sentry errors from non-LE deployments
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
The following Sentry error is coming from a deployment that isn't related to Learning Equality. I thought we had prevented this from happening previously.
Sentry Issue: STUDIO-FE4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by opening the linked Sentry issue STUDIO-FE4 and identifying which deployment produced the error. Review the deployment and Sentry context to determine how non-Learning Equality deployments are reaching this project, then verify that comparable errors no longer appear from those deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100