workbench session cold-start exceeds default timeout on slow deployments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 63
Description
Discovered during live validation. On staging, Workbench session cold-start regularly exceeds the default TIMEOUT_SESSION_START (90s) — sometimes >360s. Sessions only reached Active with VIP_TIMEOUT_SCALE=3–5 (validated working — #368).
The tests are correct; the default is just too tight for slow/cold deployments.
Options
- Raise the default
TIMEOUT_SESSION_START, and/or - Document
VIP_TIMEOUT_SCALEprominently as the knob for slow environments.
Contributor guide
No contributing guide indexed for this repository
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 locating the default TIMEOUT_SESSION_START and the handling of VIP_TIMEOUT_SCALE. Review the validated behavior from #368 and decide whether the default, the documentation, or both should change; done means slow deployments reach Active without the default timing out and the slow-environment setting is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100