Skip to content

Docs: a server stopped with SIGTERM reports Exited with code 130, not Signaled #283

Closed

Description

@Blind-Striker

What

OpenCodeServerExit after a server SIGTERM reports Exited with code 130, not Signaled: the server traps SIGTERM

Severity: nit. Seen by the builders of apps: 03.

Upstream (pinned v2.0.29)

Upstream's server handles SIGTERM itself

Proposed

Document on OpenCodeServerExit that Signaled appears only for a signal the server does not handle; a SIGTERM the server traps ends as Exited with code 130.

Source: internal DevEx evaluation of 0.9.0-preview.10 on Windows, Linux and macOS, 2026-10-14 (finding DX-22).

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions