Lack of error handling for failing QUOTA request
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Open the app
- Set up an account
- Open the account's actions menu
- Have or simulate a HTTP500 for the quota request
Expected behavior
The error is handled. Loading stops. I see an error message.
Actual behavior
Loads forever:
Mail app version
v3.4.0-beta.2
Mailserver or service
No response
Operating system
No response
PHP engine version
None
Web server
None
Database
None
Additional info
No response
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 QUOTA request triggered from the account actions menu and follow its failure path. Reproduce an HTTP 500 response and verify that loading stops and an error message is displayed; the issue is done when the app no longer remains in a loading state after the failed request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100