Skip to content

Harden shutdown, locks, pipes, and child process handling #29

Description

@foundev

Problem

Host/editor disconnects, lock poisoning, closed pipes, and child shutdown need deterministic settlement and bounded progress.

Scope

  • Audit mutex poisoning and convert it to bounded explicit errors.
  • Test reader-thread exit with commands pending.
  • Test closed editor stdout and closed host stdin.
  • Reap the child and drain/capture stderr without deadlock.
  • Add timeout protection to every shutdown path.

Acceptance

  • Host or client disconnect settles every open ACP request.
  • Shutdown cannot block indefinitely on I/O or lock ownership.

Source

  • ROADMAP.md § “Shutdown and lock robustness”

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Engineering hardening and maintenancereliabilityShutdown, recovery, and failure behaviortestingTest, conformance, and compatibility coverage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions