Skip to content

ThreadPool::enqueue ThreadPoolShutdown not handled #12306

@roberth

Description

@roberth

#12294 is a valid solution for an instance of the problem, but we'll have more instances of this.

Perhaps enqueue should always succeed, and it could return a promise from which the exception could be read.

Alternatively, we could migrate to a standard pool implementation, if possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions