docs: plan for #388 — workbench session cold-start timeout default#389
Open
posit-vip-triage[bot] wants to merge 1 commit into
Open
docs: plan for #388 — workbench session cold-start timeout default#389posit-vip-triage[bot] wants to merge 1 commit into
posit-vip-triage[bot] wants to merge 1 commit into
Conversation
posit-vip-triage
Bot
requested review from
bdeitte,
ian-flores and
statik
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #388 (no — see below: this is a plan PR, not the implementation).
This PR adds the design plan for the issue, which proposes raising the
default
TIMEOUT_SESSION_STARTfrom 90 s to 180 s and surfacingVIP_TIMEOUT_SCALEmore prominently in the README,vip.toml.example,and the website's getting-started page so that operators on slow / cold
deployments hit a sensible default first and discover the escape hatch
second instead of after a flaky run.
The plan deliberately stops short of bumping
TIMEOUT_IDE_LOADoradding a per-test override mechanism — those are flagged as separate
follow-ups.
Plan file:
thoughts/shared/plans/2026-06-15-issue-388-workbench-session-timeout-default.mdOpen questions worth flagging during plan review:
p90 cold-start to pick the number?
vip.toml.examplecallout move ride along in theimplementation PR, or split into its own docs PR?
Merging this PR will trigger an implementation PR — comment to iterate
on the plan first.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com