Document CLI I/O timeout behavior#62
Draft
rtbenfield wants to merge 1 commit into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
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.
Draft PR for visibility only. This contains the CLI I/O timeout spec and implementation plan; it is not intended to be merged.
@luanvdw tagging you for awareness.
Changes
.agents/projects/cli-io-timeouts.spec.md, defining the intended CLI behavior for stalled Prisma-controlled I/O, includingOPERATION_TIMEOUT, cancellation separation, generous defaults, and out-of-scope boundaries..agents/projects/cli-io-timeouts.plan.md, sequencing the work through a shared timeout contract, Prisma API/SDK request boundaries, long-lived inactivity boundaries, and product-doc alignment.Why
The spec chooses step-scoped and inactivity-scoped timeouts instead of a root command-wide timeout. That keeps long-running workflows such as
app logs,app domain wait,auth login, deploys, and local app runs usable while still preventing Prisma-controlled API, SDK, polling, and stream boundaries from hanging forever.