Skip to content

oracle-gaps daemon: a closing hung daemon and --stop-daemon have no cold fallback or bound #135

Open

Description

@KyleAMathews

Two daemon paths still have no cold fallback, merge-gate finding F3 on #131 (v21.2 R39, P10/I7, D61).

  1. A closing daemon whose check is hung.
    • A stop request, or a CLI of other code, sets closing and queues shutdown behind the hung check (daemon.mjs, serve).
    • Every later check hears { closing: true }. After WAIT_MS (60 s), requestDaemon throws "the package's daemon did not answer within 60 s".
    • The result is an internal error: exit 3, and no cold check.
  2. --stop-daemon against a hung daemon. stopDaemon sends its stop request with no bound, so the command never returns.

Owed, oracle-first:

  • A constructed history that closes a held daemon. Hold a check at the daemon-check pause, send a stop or a CLI of other code, then run a check and a --stop-daemon.
  • The law: each ends with one done line within the bound, and a check runs cold.
  • The hostile mutant: the current throw, and an unbounded stop.

This issue was written by Isaac.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions