learningequality / learningequality/studio
CanceledErrors are still making it into Sentry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Background
We've previously done work to prevent Sentry logging of canceled request or navigation errors. They're not something we need to address. Unfortunately, we're still seeing them.
Report
Sentry Issue: STUDIO-J49
CanceledError: canceled
at throwIfCancellationRequested (/static/studio/channel_list-0c486a31fc137cb00564.js:2:1268654)
at Axios.dispatchRequest (/static/studio/channel_list-0c486a31fc137cb00564.js:2:1268725)
at async Axios.request (/static/studio/channel_list-0c486a31fc137cb00564.js:2:1271373)
at None (/static/studio/channel_list-0c486a31fc137cb00564.js:5:49952)
at Axios.request (/static/studio/channel_list-0c486a31fc137cb00564.js:2:1271492)
...
(1 additional frame(s) were not displayed)
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 with the Sentry issue STUDIO-J49 and the cancellation stack in the built channel_list JavaScript bundle. Trace the existing handling for canceled request or navigation errors and determine why these errors still reach Sentry. Done means canceled errors no longer appear in Sentry while other errors continue to be reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100