Handle some errors better (put the host instance to maintenance mode or have an update pending)
Open
Nobody has claimed this yet.
bug
feature: frontend 🖌️
technical debt
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 350
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Currentlly errors like:
- 401
- 404
- 422
- other
don't stop polling requests and cause BFP to log out (as one of examples)
Expected behaviour
- Stop polling and interval requests
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
No file or test is named. Start by locating the frontend polling and interval-request handlers, then trace how 401, 404, 422, and other errors are handled; done means polling and interval requests stop without triggering the reported logout behavior.
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
- 35/100