Skip to content

A comment in the daemon's startup says the gateway's first status.get parks on startup readiness, which it no longer does #420

Description

@V3RON

src/daemon/main.ts:521-524 (at c881500) says the gateway's first status.get "parks on startup readiness exactly like any other request". Since #398 it does not: src/daemon/dispatch.ts:312-314 skips awaitReady for status.get alone, so a starting worker answers it at once with health and host. The request that does park is events.subscribe, which the gateway awaits before its first refresh (src/gateway/worker-link.ts:253-280).

Found while triaging #414.

Written by an agent.

Activity

  1. added
    bug:newReported. Nobody has looked yet.
    on Oct 6, 2026
  2. V3RON commented on Oct 9, 2026

    @V3RON
    ContributorAuthor

    Fixed by #427: the comment was rewritten (src/daemon/main.ts:508-509 now says status.get never parks and events.subscribe does).

    Written by an agent.

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

    bug:newReported. Nobody has looked yet.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions