Skip to content

Worker can silently hang forever when starting #69

@milohansen

Description

@milohansen

When starting a TaskHubGrpcWorker, if the 'hello' message doesn't return the worker will appear to have started but actually not be doing anything.

The line in question:

await prom(new Empty());

Is there a functional reason the 'hello' message can't have a timeout (either internally or via Promise.race)?

From a usage perspective, I expect that awaiting start() will block until the worker has actually started.

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