mirror of
https://github.com/stablyai/orca.git
synced 2026-11-05 03:27:44 +00:00
* fix(native-chat): a child's root exit is reported even during its close, and bookkeeping after it never reads as unproven - Both connections report the root process's exit once, with `expected` set when a close had begun. A close that came back unproven and whose root exits later is finished by the adapter, and its end reaches the host like any other. - A Claude close whose resume-point write fails after the exit was proven, and a Codex close whose terminal row is refused, now end the session and report the failure, instead of keeping a dead child indexed as if its exit were unproven. - A Codex close whose forced tree kill can't prove the descendants gone but saw the root exit reports the descendants and counts the root exit. - Every child exit with an identity, expected or not, is forwarded to the host. * fix(native-chat): the exit ends the child's record; an unfinished stop is the child's own close, which everyone joins - The host keeps no stored "stop still owed" record any more. A stop begins the child's close (`child.close`), which lives on the child and ends with it. A second Stop, the idle reaper, quit, a send and an option/answer/goal/rewind all join that close instead of retrying a separate obligation. - A caller waits on the close only as long as the step deadline; the close itself is never abandoned. A proof that lands after every caller stopped waiting reaches the host as the adapter's report of that exit, which ends the record through the same handler. - Once the exit is proven, draining, settling, the lease release and the adapter's acknowledgement are each attempted and reported on failure; none keeps the child on record. A start, and the handle's close, write a release that failed from this host's proof of that exit, so a failed write never refuses a send. - A start that meets a close still unverifiable is refused with `previousExitUnverifiable`, so the queued message is rejected with a send-again reason; nothing is held and nothing starts beside the old process. - The idle sweep goes back to idle reaping only. - Removes #24333's retry entry points, the wait row and its hold rule, the ask/failure cursors on the stored record, and the stop's own wake. Tests replace the #24333 unproven-stop test: a send joining an unproven close and an in-flight one, a late proof past the caller's bound, a root exiting after its close gave up, a proven exit whose resume-point write and lease release both failed, an unverifiable close rejecting the send and refusing an option change, a surviving descendant, quit and the idle reaper; and Codex's unverifiable, late-exit and joined-close cases. * fix(native-chat): a message refused because the old process's exit is unverifiable says so, and to send again The start failure for a refusal with reason `previousExitUnverifiable` reads "Orca couldn't confirm Claude's previous process ended. Send your message to try again." instead of "Claude couldn't restart." The status-row kind and the refusal reason stay in the shared lists for rows and hosts that still carry them; the catalogs keep one sentence for both. * fix(native-chat): a close's verdict is the root's exit alone, and what follows it is logged - A Claude close resolves as soon as the root's exit is proven: the session ends and its `ended` report goes out then. Saving the resume point runs afterwards and a failure is logged, so a slow or hung write never reads as an unproven exit or keeps a dead child on record. - A root that exits after its close came back unproven finishes that close through the same path as any close, so the session's child work is published as ended (background tasks and subagents no longer stay shown running for a dead agent), and a failure there is logged. - Codex logs a refused final row, and reports a root exit whose forced tree kill could not prove the rest of the tree gone the way Claude does, so the host logs it and blocks nothing. - Both adapters take the host's logger for this bookkeeping. * fix(native-chat): one handler ends every child's exit, and a join waits on the adapter's own close - One exit handler (`structured-agent-session-child-exit`) ends a child's record for an exit expected or not. `expected` only changes what the chat is told: the stop's cause, its end at the stop's ask, the settlement id, and no crash outcome row. The lease release keeps the exit's evidence; the handoff guard, lifecycle barrier, sink release and adapter acknowledgement apply to both. A Claude journal-sink failure ends in the same step as its stop, as Orca's own fault. - Joining a close is asking the adapter, whose close is memoized while it runs and bounded by its own kill escalation; the host keeps no attempt of its own and no 10 s caller bound. An ask after a close came back unproven runs the stop again. - A close's end is stamped where its stop was asked for (a repeated ask moves it), so the closed chat and failed start checks order a message accepted meanwhile after it. - A start refused because the old exit is unverifiable rejects what was queued in the same step. - The end of a close the host asked for no longer waits on the cross-session recovery chain. - The kill no longer waits for the stop event's write; the journal writes rows in order. * fix(native-chat): an exit's lease release lands whatever the length of its reason A crash's reason can carry kilobytes of the provider's stderr, and a lease whose death detail is over 512 characters fails the store's own check. The exit handler cut it, but the release a start or the chat handle's close re-derives did not, so after a crash whose own release failed every message was refused as not resumable until restart. The record's builder now cuts the detail to the record's bound, so no writer can hand it one too long. * fix(claude): a proven close waits at most 2 s for the output it already wrote Once the root's exit is proven, the close still waited for the SDK's output reader to end. Something outside the process tree that holds the output open would keep that close, and every send, Stop and quit joining it, waiting with no bound. The wait is now bounded; past it the close resolves as proven and the open output is logged. * fix(codex): an exit reported inside Orca's close keeps the reason Orca closed it for The connection reports the app-server's exit inside the close that ends it, so that report ended every Codex close and replaced the close's own reason (for example, a provider frame that could not be recorded) with the connection's stderr text in the ended record and the lease's exit evidence. The session now records Orca's close with its reason, and the exit it ends keeps that reason. The test connection reports its exit inside close the way the real one does. * fix(native-chat): quit stops delivery before it drains exit recovery Every exit now wakes delivery, and teardown drained exit recovery before it stopped delivery, so an exit settled in that window could start a fresh agent that teardown then killed. Teardown stops delivery first; queued messages wait for the next launch. * docs(native-chat): the unverifiable-exit refusal no longer names a caller's wait The caller's bounded wait was removed; the comment describes the close as it is now. * fix(native-chat): a stop whose kill did not take is logged, and the next ask kills again When a close's kill leaves the agent's root running, the host now logs it. Tests pin what a later ask does: each connection runs its whole stop again (Codex sends SIGKILL a second time), refuses input meanwhile, and proves the exit once the kill takes. * fix(native-chat): a start refused over the old process says Orca couldn't stop it The host reaches an unverifiable verdict only after its own kill left the agent's root running, on the machine that runs the agent, so the sentence now says that: "Orca couldn't stop {agent}'s previous process." The refusal reason, failure kind and wire shapes are unchanged. The host test also checks the failed kill is logged. * docs(native-chat): an unverifiable close verdict is a root that survived the kill The host's close runs where the agent runs, so lost contact never yields this verdict; the comment no longer says it does. * fix(native-chat): a kill that did not take is reported once, by whoever met it The log added at the close fired beside a Stop's own failure report for the same event. A stop still reports it through its failure; a send or option change refused over it now logs it at the refusal, the only place it is otherwise invisible. * test(native-chat): a second Stop joins a close the first could not prove and retries its kill * fix(native-chat): say a start refused beside an unstopped process plainly The rejection now reads "Couldn't stop {{agent}} from before. Send your message again to try once more." This kind has its own send-again step; every other failure keeps "Send your message to try again."
153 lines
5.9 KiB
TypeScript
153 lines
5.9 KiB
TypeScript
import { agentSessionFailureFact, providerDiagnosticOf } from '../../shared/agent-session-failure'
|
|
import type { CodexAppServerConnection } from './codex-app-server-connection-types'
|
|
import { closeProcessRegistry } from '../../shared/child-process/close-process-registry'
|
|
import {
|
|
cancelCodexAcquisitionAttempt,
|
|
type CodexAcquisitionRegistry,
|
|
type CodexSession,
|
|
type CodexStructuredSessionEvent
|
|
} from './codex-structured-session-state'
|
|
import type { StructuredAgentSessionEndedEvent } from '../native-chat/agent-session-wire/structured-agent-session-adapter'
|
|
import type { StructuredAgentSessionLogger } from '../native-chat/agent-session-wire/structured-agent-session-logger'
|
|
|
|
export function handleCodexSessionExit(input: {
|
|
sessions: Map<string, CodexSession>
|
|
sessionId: string
|
|
connection: CodexAppServerConnection | null
|
|
error: Error
|
|
/** Set for the end of a close Orca began: by that close, or by the root's own exit report. */
|
|
closedByOrca?: true
|
|
prompts?: CodexSession['prompts']
|
|
onEvent?: (event: CodexStructuredSessionEvent) => void
|
|
logger?: StructuredAgentSessionLogger
|
|
}): boolean {
|
|
const session = input.sessions.get(input.sessionId)
|
|
if (!session || session.connection !== input.connection || session.ended) {
|
|
input.prompts?.clear()
|
|
return false
|
|
}
|
|
session.exitObservedAt ??= Date.now()
|
|
// Before the admission check: the child is gone whether or not its end was admitted.
|
|
session.turnOpenWaits.releaseAll()
|
|
const event: StructuredAgentSessionEndedEvent = {
|
|
type: 'ended',
|
|
sessionId: input.sessionId,
|
|
// The connection reports the exit inside the close it ends; the close's own reason is the why.
|
|
reason: ((input.closedByOrca && session.orcaClose?.reason) || input.error).message,
|
|
// Only the child's own exit blames Codex; a close Orca made, for any reason, is Orca's.
|
|
failure: input.closedByOrca
|
|
? agentSessionFailureFact('hostFault')
|
|
: agentSessionFailureFact('providerExited', { detail: providerDiagnosticOf(input.error) }),
|
|
cause: session.orcaClose?.requested ? 'requested-close' : 'unexpected-exit',
|
|
fence: session.fence,
|
|
acquisitionGeneration: session.acquisitionGeneration,
|
|
observedAt: session.exitObservedAt
|
|
} as const
|
|
// A synchronous sink rejection (usually backpressure) leaves the terminal rows to the host's
|
|
// exit settlement, which writes its own bounded fallback. The exit itself is observed, so the
|
|
// session ends either way: holding a dead child as unproven over a refused row would strand it.
|
|
const admission = session.translator?.handle(event) ?? { accepted: true }
|
|
if (!admission.accepted) {
|
|
input.logger?.warn("Codex's final rows were refused; the host settles the turn instead", {
|
|
scope: 'codex-exit-rows',
|
|
sessionId: input.sessionId,
|
|
reason: admission.reason
|
|
})
|
|
}
|
|
session.ended = true
|
|
// Nothing can echo for this child any more; the journal's pending-submission
|
|
// recovery is what settles the sends these were armed for.
|
|
session.dispatchEchoes.clear()
|
|
session.backgroundTasks.clear()
|
|
// Every close path funnels here, so the session's children end with it on each one.
|
|
session.backgroundTasks.publishChildWork()
|
|
session.unbindReadingControl?.()
|
|
input.onEvent?.(event)
|
|
session.prompts.clear()
|
|
session.translator?.dispose()
|
|
return true
|
|
}
|
|
|
|
export async function closeCodexPublishedSession(
|
|
sessions: Map<string, CodexSession>,
|
|
sessionId: string,
|
|
onEvent?: (event: CodexStructuredSessionEvent) => void,
|
|
options?: {
|
|
logger?: StructuredAgentSessionLogger
|
|
requestedClose?: boolean
|
|
expectedFence?: number
|
|
expectedAcquisitionGeneration?: string
|
|
unexpectedReason?: Error
|
|
}
|
|
): Promise<boolean> {
|
|
const session = sessions.get(sessionId)
|
|
if (!session) {
|
|
return true
|
|
}
|
|
if (
|
|
(options?.expectedFence !== undefined && session.fence !== options.expectedFence) ||
|
|
(options?.expectedAcquisitionGeneration !== undefined &&
|
|
session.acquisitionGeneration !== options.expectedAcquisitionGeneration)
|
|
) {
|
|
return false
|
|
}
|
|
// Sink-failure recovery force-closes the child but must preserve the
|
|
// observed-exit cause so host lease settlement runs as an unexpected death.
|
|
session.orcaClose = {
|
|
requested: options?.requestedClose ?? true,
|
|
reason: options?.unexpectedReason ?? new Error('codex session closed')
|
|
}
|
|
// Keep the session indexed until the child exit is observed. A timeout or
|
|
// failed kill must leave the live connection available for a safe retry.
|
|
const exited = await session.connection.close()
|
|
if (exited !== true) {
|
|
return false
|
|
}
|
|
if (!session.ended) {
|
|
handleCodexSessionExit({
|
|
sessions,
|
|
sessionId,
|
|
connection: session.connection,
|
|
error: session.orcaClose.reason,
|
|
closedByOrca: true,
|
|
prompts: session.prompts,
|
|
...(onEvent ? { onEvent } : {}),
|
|
...(options?.logger ? { logger: options.logger } : {})
|
|
})
|
|
}
|
|
sessions.delete(sessionId)
|
|
return true
|
|
}
|
|
|
|
export async function closeCodexSession(
|
|
sessionId: string,
|
|
sessions: Map<string, CodexSession>,
|
|
acquisitions: CodexAcquisitionRegistry,
|
|
onEvent?: (event: CodexStructuredSessionEvent) => void,
|
|
logger?: StructuredAgentSessionLogger
|
|
): Promise<boolean> {
|
|
const attempt = acquisitions.get(sessionId)
|
|
if (!(await cancelCodexAcquisitionAttempt(attempt))) {
|
|
return false
|
|
}
|
|
if (attempt) {
|
|
acquisitions.deleteIfCurrent(sessionId, attempt)
|
|
}
|
|
return closeCodexPublishedSession(sessions, sessionId, onEvent, logger ? { logger } : {})
|
|
}
|
|
|
|
export async function closeAllCodexSessions(
|
|
sessions: Map<string, CodexSession>,
|
|
acquisitions: CodexAcquisitionRegistry,
|
|
close: (sessionId: string) => Promise<boolean>
|
|
): Promise<void> {
|
|
acquisitions.close()
|
|
await closeProcessRegistry({
|
|
attempts: 3,
|
|
hasEntries: () => sessions.size > 0 || acquisitions.size > 0,
|
|
entryIds: () => new Set([...sessions.keys(), ...acquisitions.sessionIds()]),
|
|
closeEntry: close,
|
|
failureMessage: 'codex structured session shutdown could not prove every child stopped'
|
|
})
|
|
}
|