Skip to content

Better error messages when BOOST_ASIO_CONCURRENCY_HINT_UNSAFE is set #376

@mzimbres

Description

@mzimbres

We should either support BOOST_ASIO_CONCURRENCY_HINT_UNSAFE or improve the error message when it is set (or any other hint that prevents async_resolve). At the moment constructing an io_context with BOOST_ASIO_CONCURRENCY_HINT_UNSAFE produces the following error messages

(Boost.Redis) Trying to connect to Redis server at 127.0.0.1:6379 (TLS disabled)
(Boost.Redis) Connect: hostname resolution failed: Operation not supported [system:95]
(Boost.Redis) Failed to connect to Redis server at 127.0.0.1:6379 (TLS disabled): Operation not supported [system:95]
(Boost.Redis) Trying to connect to Redis server at 127.0.0.1:6379 (TLS disabled)
(Boost.Redis) Connect: hostname resolution failed: Operation not supported [system:95]
(Boost.Redis) Failed to connect to Redis server at 127.0.0.1:6379 (TLS disabled): Operation not supported [system:95]
(Boost.Redis) Trying to connect to Redis server at 127.0.0.1:6379 (TLS disabled)
(Boost.Redis) Connect: hostname resolution failed: Operation not supported [system:95]
(Boost.Redis) Failed to connect to Redis server at 127.0.0.1:6379 (TLS disabled): Operation not supported [system:95]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions