Repository navigation
Terminal exit error handling - #116
Closed
juliusmarminge wants to merge 1 commit into
Closed
juliusmarminge wants to merge 1 commit into
juliusmarminge wants to merge 1 commit into
Conversation
Co-authored-by: Julius Marminge <juliusmarminge@users.noreply.github.com>
Contributor
|
Cursor Agent can help with this pull request. Just |
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
17 tasks
radroid
referenced
this pull request
in radroid/t3code
Aug 8, 2026
…eep reopened Fallout from #56, caught by re-checking the alert list after it merged rather than assuming the count only goes down. Before the sweep the tree had one nanoid@3.3.12, and GHSA #115/#116 against it sat auto-dismissed by GitHub's auto-triage rule — it was scoped as a development dependency. astro 7.2.0 restructured its tree, adding an already-fixed nanoid@3.3.17 alongside the old copy and flipping that copy's scope to runtime, which took it out from under the rule and reopened both alerts. The sweep did not introduce a vulnerability — 3.3.12 was there before and was always affected — but it turned a suppressed finding into a live one. One override, "nanoid@3": ^3.3.17, dedupes onto the version already in the tree. Both advisories want <= 3.3.17, so this clears both. Ledger figures refreshed in the same commit per SEAMS.md's self-reference rule.
github-actions Bot
referenced
this pull request
in radroid/t3code
Aug 10, 2026
…eep reopened Fallout from #56, caught by re-checking the alert list after it merged rather than assuming the count only goes down. Before the sweep the tree had one nanoid@3.3.12, and GHSA #115/#116 against it sat auto-dismissed by GitHub's auto-triage rule — it was scoped as a development dependency. astro 7.2.0 restructured its tree, adding an already-fixed nanoid@3.3.17 alongside the old copy and flipping that copy's scope to runtime, which took it out from under the rule and reopened both alerts. The sweep did not introduce a vulnerability — 3.3.12 was there before and was always affected — but it turned a suppressed finding into a live one. One override, "nanoid@3": ^3.3.17, dedupes onto the version already in the tree. Both advisories want <= 3.3.17, so this clears both. Ledger figures refreshed in the same commit per SEAMS.md's self-reference rule.
radroid
referenced
this pull request
in radroid/t3code
Aug 10, 2026
…eep reopened Fallout from #56, caught by re-checking the alert list after it merged rather than assuming the count only goes down. Before the sweep the tree had one nanoid@3.3.12, and GHSA #115/#116 against it sat auto-dismissed by GitHub's auto-triage rule — it was scoped as a development dependency. astro 7.2.0 restructured its tree, adding an already-fixed nanoid@3.3.17 alongside the old copy and flipping that copy's scope to runtime, which took it out from under the rule and reopened both alerts. The sweep did not introduce a vulnerability — 3.3.12 was there before and was always affected — but it turned a suppressed finding into a live one. One override, "nanoid@3": ^3.3.17, dedupes onto the version already in the tree. Both advisories want <= 3.3.17, so this clears both. Ledger figures refreshed in the same commit per SEAMS.md's self-reference rule.
piero-dev25
added a commit
to piero-dev25/devgame
that referenced
this pull request
Aug 12, 2026
… provider matrix, architecture drafts Five-lane research wave against the charter. Headline: the canonical tool server is SHIPPED infrastructure, not a hypothesis — the server hosts /mcp and all five provider adapters inject its credential; generation is a toolkit directory, not a transport project. Async is forced by Codex's 60s tool timeout: generate_* returns a job id, the SERVER owns the provider poll loop. Persistence splits by mutability (decisions event-sourced on the existing project aggregate; progress in-memory per the fork's own registry precedent); GeneratedAsset must NOT live in thread-scoped attachmentsDir. The McpCapability widening (pingdotgg#116) lands as its own PR before any tool. Tripo over Meshy for the 3D spike; ComfyUI over Unsloth for local image. Unsloth notes are clean-room (AGPL boundary stated in-file). agent-tooling.md carries a reconciliation banner: its repo-specific findings were measured against the wrong codebase and are superseded; protocol-level content verified valid. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
piero-dev25
added a commit
to piero-dev25/devgame
that referenced
this pull request
Aug 12, 2026
…pingdotgg#116, V2 prerequisite) The vendor PreviewAutomationUnavailableError hardcodes capability: Schema.Literal("preview") inside packages/contracts and is the declared failure of every preview tool — widening that literal was the trap. requireMcpCapability now raises a fork-owned McpCapabilityUnavailableError; the preview toolkit's invoke translates it back to the vendor error at its one call site (total translation — that site only ever requests preview), so every preview tool's declared failure stays honest and packages/contracts has a provably empty diff. The capability GRANT stays preview-only (registry comment points at docs/v2/OWNER_DOCKET.md D2 — pending owner ruling). Red-proven three ways, including the trap itself: against the pre-widening code the generation tests fail with the vendor schema literally rejecting the second capability value. 43 mcp-area tests green; server + contracts typecheck clean; contracts test suite 228 green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Auto-close the terminal on exit and suppress benign write errors that occur during shutdown.
Commands like
exitshould gracefully close the terminal without displaying error messages, treating such "failures" as normal terminal behavior rather than hard errors.Note
Handle terminal exit errors by invoking
components.TerminalViewportProps.onCloseTerminalfromcomponents.TerminalViewportand remove system messages in ThreadTerminalDrawer.tsxAdd
onCloseTerminaltocomponents.TerminalViewportPropsand call it when write errors matchterminal-errors.isIgnorableTerminalWriteErroror onexited; updateThreadTerminalDrawerto pass the callback; add tests forisIgnorableTerminalWriteErrorand implement the utility in terminal-errors.ts.📍Where to Start
Start with the
TerminalViewportcomponent changes in ThreadTerminalDrawer.tsx, then reviewisIgnorableTerminalWriteErrorin terminal-errors.ts.Macroscope summarized 7dc0ff1.