learningequality / learningequality/studio
Determine cause of unknown status code network errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
We've been getting very many errors that have failed to pull the response status code from the axios request, resulting errors like the following. Is this a legitimate error or something we can ignore? For the time being, errors matching this will not be sent to Slack's #studio-sentry channel
Example Sentry Issue: STUDIO-FVG
Error: Network Error: [0] /api/sync/
at Error: Network Error: [0] (/api/sync/)
at None (/static/studio/channel_edit-92f9743d4a1212543f61.js:8:2863167)
at Hub.withScope (/static/studio/channel_edit-92f9743d4a1212543f61.js:8:2855621)
at withScope (/static/studio/channel_edit-92f9743d4a1212543f61.js:8:2862097)
at None (/static/studio/channel_edit-92f9743d4a1212543f61.js:8:2862973)
...
(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 by tracing the axios request for /api/sync/ and the handling that produces “Network Error: [0]”; use the linked Sentry issue as the reproduction evidence. Determine whether the status-less response is expected or actionable, then document the cause and whether suppressing these errors from Slack’s #studio-sentry channel is appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100