Proper timeout detections of large app install
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: apps management
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Now that we have some large apps not all connections are fast enough to install them with the web timeout.
Hence I would propose:
- When an app is installing and we get back a server error after more than 10 seconds (or something like that) we assume it times out. And we tell the user to try to manually do this and link to the docs.
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
The issue concerns app installation through the web timeout path, but names no files or tests. Start by locating the server-side app installation handling and its response to server errors after slow installs. Done means slow large-app installs are identified as timeouts, the user is directed to manual installation, and the relevant documentation is linked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100